Code builder
Skill Razaib-khan/ForgeWeave/src/forgeweave/templates/gemini/.gemini/skills/code-builder
Behavioral execution framework for AI agents — define deterministic, portable skills & agents across OpenCode, Claude Code, Gemini CLI, and Qwen Code.
npx -y skills add Razaib-khan/ForgeWeave --skill code-builderAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Translates plans into working code structures with architecture decisions, folder layout, and implementation strategy
SKILL.md
2.5 KB, as published. Nobody here has run it
Code Builder
Purpose
Take a structured plan and produce working, well-organized code. Makes architecture decisions (framework choice, folder structure, module boundaries), generates the code, and verifies it compiles or passes basic checks.
When to Use
- A
plannerskill has produced an execution plan - The user asks to "implement" or "build" a feature from requirements
- Scaffolding a new module, component, or service
- Translating architecture decisions into concrete code
When Not to Use
- The code change is a simple rename or refactor — use
refactor-engine - Only tests are needed — use
test-generator - The task is debugging an existing issue — use
debugger
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
plan | object | Yes | The execution plan from the planner skill |
existing_code | string | No | Description of existing codebase structure |
standards | array | No | Coding standards to follow (e.g., TypeScript strict, PEP 8) |
Expected Outputs
| Output | Description |
|---|---|
| New or modified files | Working code implementing the plan |
| Folder structure | Organized module layout |
| Architecture notes | Key decisions made during implementation |
Exact Workflow Steps
- Review the plan and understand the architecture
- Create folder structure matching project conventions
- Implement each module following existing patterns
- Add type annotations and documentation as code is written
- Verify the code compiles or passes syntax checks
- Run existing tests to confirm no regressions
Required Checks
- Code compiles without errors
- Existing tests still pass
- Code follows project conventions (naming, imports, formatting)
- New exports are properly typed
Failure Modes
| Failure Condition | Response |
|---|---|
| Code doesn't compile | Fix type errors and re-verify |
| Existing tests fail | Identify root cause and fix before continuing |
| Architecture decision contradicts plan | Flag to planner for resolution |
References
| Reference | Path |
|---|---|
| Planner skill | ../planner/SKILL.md |
| Test Generator skill | ../test-generator/SKILL.md |