scaffold

Survey existing code conventions and emit a minimal matching module skeleton.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/nokusukun/sublime --skill scaffold-nokusukun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scaffold
Source: https://github.com/nokusukun/sublime/tree/main/scaffold
Command: npx skills add https://github.com/nokusukun/sublime --skill scaffold-nokusukun

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? The scaffold skill helps teams jump-start new modules or features by learning the codebase conventions (naming, structure, imports, error handling, test layout) and emitting the smallest working skeleton that matches local conventions. ## Core Features & Use Cases

  • Survey existing code examples to extract conventions and patterns used by the repository.
  • Validate the current Code Context before generating anything to ensure alignment with project invariants.
  • Emit the smallest skeleton that mirrors the observed conventions, including file layout, naming, and test placement.
  • Provide a clear hand-off: list missing pieces and the next concrete steps (first call site, first test, first integration).
  • Support iterative refinement by re-running with updated context or targets. ### Quick Start Invoke the scaffold verb with a target description to emit the smallest skeleton that matches the repository conventions.

Frequently Asked Questions about scaffold

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap a new module that matches existing codebase conventions?

To bootstrap a new module with matching codebase conventions, survey existing code examples to extract naming, structure, imports, and test layout patterns, then emit a minimal skeleton that mirrors those conventions. This ensures the new module integrates smoothly without requiring global changes.

What is the best way to generate a skeleton for a new feature without breaking project conventions?

Generating a convention-aligned skeleton requires inspecting existing examples for naming, error handling, and test layout before creating files. The smallest working skeleton is emitted with a clear hand-off listing missing pieces and next concrete steps like the first call site or first test.

How do I ensure my new module's file layout and imports align with repository conventions?

Ensuring file layout and imports align with repository conventions involves validating the current Code Context against project invariants before generation. By surveying existing examples, the scaffolding process extracts structural patterns and applies them to produce a ready-to-commit module skeleton.

Can I scaffold a new module iteratively if the project context changes?

Yes, you can scaffold a module iteratively by re-running the generation with updated context or targets. This allows the emitted skeleton to be refined as project conventions evolve, ensuring the module structure continuously aligns with the latest codebase invariants.

Does scaffolding a module with extracted conventions require any global codebase changes?

No, scaffolding a module with extracted conventions requires no global changes to the codebase. The process solely inspects existing examples to produce a minimal, ready-to-commit skeleton, leaving the rest of the project untouched while ensuring smooth integration.