Agent skill · writing content · aiskillstore
generate-output
Create the deliverable (code, documentation, tests, content) following the user's standards and best practices. Use after validation passes to actually build the work product.
Why this skill is useful
Generates deliverables based on user-defined standards and patterns, which the AI wouldn't reliably create on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Generate Output Skill Purpose Transforms validated requirements into actual deliverables (code, documentation, tests, content). This skill follows the user's principles and common patterns defined in their standards. What to Do 1. Read the validated requirements from the previous step 2. Load the project type's standards (from standards.json) to understand their principles and patterns 3. Generate the deliverable based on: User's specific requirements Their saved principles for this project type Their common patterns (what they always do) Best practices for this type of work 4. Follow their patterns - If they defined common patterns, include them: Example: "Always include error handling" → include it Example: "Always write JSDoc comments" → include it 5. Create complete, ready-to-use output Project Type Specific Guidance Code Features Write complete, production-ready code Include prop types, type annotations, or schema validation Include error handling Add comments for complex logic Include example usage or test case Follow their coding standards (naming, structure, patterns) Documentation Clear structure with headers Include purpose/overview at top Add examples and use cases Include troubleshooting if applicable Link related documentation Use their documentation template if defined Refactoring Show the "before" code Show the "after" refactored code Explain the improvements Highlight what changed and why Include the refactored code ready to copy Note any behavioral changes Test Suite Write comprehensive tests Test happy path and edge cases Use descriptive test names Include setup/teardown as needed Follow their testing conventions Ensure tests are maintainable Content Creation Compelling introduction Clear structure with sections Use headers, lists, and examples Include practical examples Conclusion with key takeaways Appropriate tone for audience Process 1. Review requirements 2. Load their standards using StandardsRepository 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/generate-output