Generate multi-file Simple module scaffolding with .spl files and SPipe BDD tests.
npx skills add https://github.com/ormastes/Spipe --skill stitch-ormastes
Please help me install this Agent Skill. Skill: stitch Source: https://github.com/ormastes/Spipe/tree/main/doc/00_llm_process/skill_command/skills/gemini/stitch Command: npx skills add https://github.com/ormastes/Spipe --skill stitch-ormastes
It solves the slow, error-prone work of hand-creating consistent multi-file module scaffolding when you need new Simple features or subsystems.
Ask the system to stitch a new feature module scaffold for your chosen src/ location, and it will generate the complete .spl structure, tests, and doc stubs.
High-intent search queries and answers about installing and using this skill.
To generate multi-file Simple module scaffolding, you provide a feature name and src/ location. The system plans module placement and dependency-aware file lists, then produces .spl modules and required mod.spl files across lib/, compiler/, and app/ trees.
Module scaffolding in the Simple language is the automated creation of consistent .spl file structures, tests, and documentation stubs. You need it when starting new features or subsystems to avoid slow, error-prone manual file creation and ensure Simple-specific code generation rules are followed.
To scaffold BDD test specs and documentation stubs, the system generates matching test/ spec files in SPipe BDD format and adds stub docs in doc/05_design and doc/04_architecture directories automatically during the .spl module generation workflow.
Yes, Simple code generation enforces language-specific rules including generics syntax, constructor conventions, pattern binding, and Result-based error handling with the ? operator. It uses composition over inheritance and real placeholder implementations without pass_todo.
Yes, you can use Stitch MCP templates to target module placement across lib/, compiler/, and app/ directory trees. The generation process plans dependencies and file structure before writing code to ensure correct module placement.
The best way to structure a new Simple feature module is using a phase-based generation approach that plans module placement and dependency-aware file lists before writing any .spl code, ensuring consistent architecture across src/ trees, tests, and documentation stubs.
ccfCodify Nx workspace patterns for monorepo setup, boundary enforcement, and caching.
ormastesGenerate detailed design documents and agent task breakdowns from approved requirements and architecture.
ormastesMap Simple subprojects to SPipe/SPstack pipeline paths with verification steps.
dhruvinrsoniDefine testing pyramid, coverage targets, and test conventions for projects.
