codeplain-ai/plain-forge
28 skills1.1k installs1.5k starsGitHub
Install
npx skills add https://github.com/codeplain-ai/plain-forgeSkills in this repo
1Consolidate ConceptsGathers concept definitions scattered across ***plain modules into a single shared import module. A developer uses it to centralize duplicated or spread-out domain concepts as a structural refactor.45installs2Create Requires ModuleCreates a ***plain module that uses `requires` to depend on another module in the build chain. A developer uses it to build on top of a previously built module, inheriting its code and functional specs.43installs3Resolve Spec Conflictresolve-spec-conflict is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.43installs4Add Acceptance TestAdds acceptance tests as verification criteria under a functional spec in a ***plain spec file. A developer uses it to attach testable success criteria to a spec whose behavior is non-obvious.42installs5Add ConceptAdds a concept, entity, or domain term to the ***definitions*** section of a ***plain spec file. A developer uses it to define a new domain concept while avoiding naming collisions and circular references.42installs6Add FeatureTakes a plain-English feature request and incrementally writes ***plain specs one functionality at a time via a question-and-write loop. A developer uses it to add a feature to an existing ***plain project.42installs7Add Implementation RequirementAdds a non-functional implementation requirement to the ***implementation reqs*** section of a ***plain spec file. A developer uses it to steer code generation with technology, architecture, or coding-standard guidance.42installs8Add ResourceAdds a linked external file reference to a ***plain spec using markdown link syntax. A developer uses it to reference a JSON schema, API spec, or data file from within a spec section.42installs9Add TemplateCreates or includes a parameterized Liquid template in a ***plain spec file for reusing spec content across modules. A developer uses it when the same spec structure is needed in multiple .plain files with different values.42installs10Add Test RequirementAdds a conformance test requirement to the ***test reqs*** section of a ***plain spec file. A developer uses it to specify how conformance tests should be written and run.42installs11Analyze 2 Func SpecsAnalyzes two functional specs from a ***plain spec file to determine if they conflict. A developer uses it to check whether two specific requirements are compatible or to debug a suspected conflict.42installs12Analyze If Func Spec Too ComplexAnalyzes a drafted functional spec to determine if it exceeds the renderer's 200-LOC complexity limit. A developer uses it after drafting a spec to verify it fits before insertion.42installs13Break Down Func SpecBreaks a too-complex functional spec into smaller specs that each imply at most 200 lines of code. A developer uses it when a spec is flagged TOO COMPLEX or is suspected of being too large.42installs14Create Import ModuleCreates a ***plain import module that provides shared definitions, implementation reqs, and test reqs for other modules. A developer uses it to share concepts or common requirements across multiple modules.42installs15Debug SpecsInvestigates a bug in the running app by reading generated code, tracing it to the specs, and fixing only the .plain files. A developer uses it when the app shows unexpected behavior, crashes, or failing tests.42installs16Forge PlainRuns an end-to-end QA interview then authors complete ***plain specification files for a new project. A developer uses it to build something new from scratch via a one-question-then-write loop.42installs17Load Plain ReferenceLoads the full ***plain language reference into context, covering syntax, section types, frontmatter, templates, and the module model. A developer uses it before authoring, editing, or debugging any .plain files.42installs18Refactor ModuleSplits a large ***plain module into smaller modules grouped by logical domain, connected via a requires chain. A developer uses it when a module has grown too broad across distinct concerns.42installs19Implement Conformance Testing ScriptGenerates a language-agnostic conformance-test runner script (Bash or PowerShell) for a ***plain build folder. A developer uses it to add a conformance-test runner for a new language to a ***plain project.40installs20Implement Prepare Environment ScriptGenerates a language-agnostic prepare-environment script (Bash or PowerShell) that runs one-time setup before conformance tests. A developer uses it to stage builds and pre-warm caches for a new language in a ***plain project.39installs21Implement Unit Testing ScriptGenerates a language-agnostic unit-test runner script (Bash or PowerShell) for a ***plain build folder. A developer uses it to add a unit-testing script for a new language to a ***plain project.39installs22Add Functional SpecAdds a single functional spec to the ***functional specs*** section of a ***plain spec file with complexity and conflict checks. A developer uses it whenever exactly one new functional spec must be authored.38installs23Add Functional SpecsAdds multiple functional specs to a ***plain spec file in one batch, running per-spec complexity and conflict checks. A developer uses it to author several related functional specs at once.37installs24Analyze Func SpecsAnalyzes a batch of functional specs from a ***plain spec file to find which pairs conflict. A developer uses it to check many specs at once instead of pair-by-pair.33installs25Init Config FileBuilds and finalizes the config.yaml file(s) the codeplain renderer consumes. A developer uses it at the end of forge-plain or add-feature, or whenever a project's config.yaml needs to be regenerated.32installs26Plain HealthcheckVerifies a ***plain project is ready to render by checking config.yaml, script paths, and running codeplain dry-runs. A developer uses it as the closing gate whenever the project is finalized.32installs27Check Plain EnvReads a ***plain project to determine every tool, runtime, and service the host needs, then probes the machine and reports what is missing. A developer uses it before first rendering or testing a ***plain project on a new machine.30installs28Run CodeplainLaunches a codeplain render and supervises it end-to-end by tailing logs and watching generated code. A developer uses it to actually render specs with live monitoring and pathology detection.14installs