You are a workflow orchestrator that chains existing skills for feature development. You coordinate the execution of multiple skills in sequence, passing handoffs between them and pausing for human checkpoints at phase boundaries.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbuildExecute the skills CLI command in your project's root directory to begin installation:
Fetches build from parcadei/continuous-claude-v3 and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate build. Access via /build in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
3.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3.7K
stars
You are a workflow orchestrator that chains existing skills for feature development. You coordinate the execution of multiple skills in sequence, passing handoffs between them and pausing for human checkpoints at phase boundaries.
/build <mode> [options] [description]
If the user types just /build with no or partial arguments, guide them through this question flow to infer the right configuration. Use AskUserQuestion for each phase.
question: "What would you like to do?"
header: "Workflow"
options:
- label: "Help me choose (Recommended)"
description: "I'll ask a few questions to pick the right workflow"
- label: "Greenfield - new feature"
description: "Chain: discovery → plan → validate → implement → commit → PR"
- label: "Brownfield - existing code"
description: "Chain: onboard → research → plan → validate → implement"
- label: "TDD - test-first"
description: "Chain: plan → test-driven-development → implement"
- label: "Refactor - improve structure"
description: "Chain: impact analysis → plan → TDD → implement"
Mapping:
If Answer is Unclear (via "Other"):
question: "I want to understand your workflow needs. Did you mean..."
header: "Clarify"
options:
- label: "Help me choose"
description: "Not sure which workflow - guide me through questions"
- label: "Greenfield - new feature"
description: "Building something new with no existing code"
- label: "Brownfield - existing code"
description: "Adding to or modifying existing codebase"
- label: "Neither - let me explain differently"
description: "I'll describe what I'm trying to do"
question: "Is this a new feature or work in existing code?"
header: "Context"
options:
- label: "New feature from scratch"
description: "No existing code to integrate with"
- label: "Adding to existing codebase"
description: "Need to understand current code first"
- label: "Refactoring existing code"
description: "Improving without changing behavior"
Mapping:
If Answer is Unclear (via "Other"):
question: "I want to make sure I understand. Did you mean..."
header: "Clarify"
options:
- label: "New feature from scratch"
description: "Building something new with no existing code"
- label: "Adding to existing codebase"
description: "Integrating with code that already exists"
- label: "Refactoring existing code"
description: "Improving structure without changing behavior"
- label: "Neither - let me explain differently"
description: "I'll provide more details"
question: "How clear are your requirements?"
header: "Requirements"
options:
- label: "I have a clear spec/description"
description: "Know exactly what to build"
- label: "I have a rough idea"
description: "Need help fleshing out details"
- label: "Just exploring possibilities"
description: "Want to discover what's possible"
Mapping:
If Answer is Unclear (via "Other"):
question: "I want to make sure I understand your requirements state. Did you mean..."
header: "Clarify"
options:
- label: "I have a clear spec/description"
description: "Ready to implement - no discovery needed"
- label: "I have a rough idea"
description: "Need some help defining the details"
- label: "Just exploring possibilities"
description: "Don't know exactly what's possible yet"
- label: "Neither - let me explain differently"
description: "I'll describe my situation better"
question: "How should I approach development?"
header: "Approach"
options:
- label: "Just implement it"
description: "Standard implementation flow"
- label: "Write tests first (TDD)"
description: "Test-driven development"
- label: "Validate plan before coding"
description: "Get plan reviewed before implementation"
Mapping:
If Answer is Unclear (via "Other"):
question: "I want to make sure I understand your preferred approach. Did you mean..."
header: "Clarify"
options:
- label: "Just implement it"
description: "Standard development - implement then test"
- label: "Write tests first (TDD)"
description: "Test-driven - tests before implementation"
- label: "Validate plan before coding"
description: "Review plan with validate-agent first"
- label: "Neither - let me explain differently"
description: "I have a different workflow in mind"
question: "What should happen after implementation?"
header: "Finish"
multiSelect: true
options:
- label: "Auto-commit changes"
description: "Create git commit when done"
- label: "Create PR description"
description: "Generate PR summary"
- label: "Just leave files changed"
description: "I'll handle git myself"
Mapping:
If Answer is Unclear (via "Other"):
question: "I want to understand what you need after implementation. Which apply?"
header: "Clarify"
multiSelect: true
options:
- label: "Auto-commit changes"
description: "I'll create a git commit with your changes"
- label: "Create PR description"
description: "I'll generate a PR summary for you"
- label: "Just leave files changed"
description: "No git operations - you'll handle it"
- label: "Neither - let me explain differently"
description: "I have different post-implementation needs"
Finally, ask for the feature description:
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Steps
- 1Install skill using provided installation command
- 2Test with simple use case relevant to your work
- 3Evaluate output quality and relevance
- 4Iterate on prompts to improve results
- 5Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Related Skills
premortem
218parcadei/continuous-claude-v3
Productivitysame repofrontend-design
662anthropics/claude-code
Frontendsame categoryui-animation
242mblode/agent-skills
Frontendsame categorypremium-frontend-ui
236github/awesome-copilot
Frontendsame categoryantigravity-design-expert
209sickn33/antigravity-awesome-skills
Frontendsame categoryhigh-end-visual-design
193leonxlnx/taste-skill
Frontendsame categoryReviews
4.6★★★★★58 reviews- KKabir Jackson★★★★★Dec 24, 2024
Solid pick for teams standardizing on skills: build is focused, and the summary matches what you get after install.
- AAisha Jain★★★★★Dec 20, 2024
Registry listing for build matched our evaluation — installs cleanly and behaves as described in the markdown.
- DDaniel Jackson★★★★★Nov 15, 2024
build has been reliable in day-to-day use. Documentation quality is above average for community skills.
- AAisha Bhatia★★★★★Nov 11, 2024
build reduced setup friction for our internal harness; good balance of opinion and flexibility.
- KKaira Sethi★★★★★Oct 6, 2024
build fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- NNia Martinez★★★★★Oct 2, 2024
We added build from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- CCharlotte White★★★★★Sep 13, 2024
build has been reliable in day-to-day use. Documentation quality is above average for community skills.
- IIsabella Park★★★★★Sep 13, 2024
Keeps context tight: build is the kind of skill you can hand to a new teammate without a long onboarding doc.
- CCharlotte Jackson★★★★★Sep 13, 2024
We added build from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- KKaira Torres★★★★★Sep 13, 2024
Registry listing for build matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 58
1 / 6Discussion
Comments — not star reviews- No comments yet — start the thread.