Plugins
3 plugins@dotnet
Dotnet Template Engine
.NET Template Engine skills: template discovery, project scaffolding, and template authoring.
6 skills · plugin
@microsoft
Microsoft 365 Agents Toolkit
Toolkit for building and evaluating Microsoft 365 Copilot declarative agents — scaffolding, JSON manifest development, capability configuration, and eval workflows.
6 skills · plugin
curated
Build MVP from Spec
Turn a design or spec document into a working MVP by planning thin vertical slices, scaffolding, then building iteratively with TDD and gated commits.
5 skills · plugin
Results for “scaffolding”
6 skills
affaan-m Orch Build Mvp
Turn a design or spec document into a working MVP by planning thin vertical slices, scaffolding the first slice, then building iteratively with test-driven development and gated commits.
226k
dotnet Template Instantiation
Creates .NET projects from templates with validated parameters, Central Package Management adaptation, and multi-project composition.
4k
alirezarezvani Spec To Repo
Turns a natural-language project specification into a complete, runnable starter repository with real code, tests, and CI configuration for any stack.
20.4k · bundle
More results
alirezarezvani Product Skills
Routes product requests to one of 12 bundled skills covering prioritization, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, and SaaS scaffolding.
20.4k
hekivo Superpowers Sage Building
Plan-driven implementation in Sage/Acorn — reads docs/plans/ directory, implements components from approved sub-plans, runs scaffold generators (lando acorn acf:block), commits incrementally, auto-invokes block-scaffolding per ACF block, runs lando flush and lando theme-build after changes; full PR workflow with sage-reviewer gate. Invoke for: "/building", "implement from the plan", "implement from the plan", "build from the plan", "execute the plan", "start building", "code this feature". Skip when: there is no approved plan yet — run /architecture-discovery then /plan-generator first.
13
subvisual Project Context
Use when a project's durable context needs to be seeded or refreshed — creating or updating docs/product/context.md (overview + digest + source index + glossary + Know/Don't-Know ledger + design context + technical context) in the target repo; when a project has no context layer yet (Stage-0 setup); when domain terminology is still forming or has drifted; after a meeting, new evidence batch, or scope change that outdates the current context. Also use to ingest new docs/product/input/ batches into the digest. Do not use for repo scaffolding or CI setup, for writing the discovery plan, PRD, or epics (use discovery-plan, prd-writer, epics), or for creating or revising Jobs to be Done — this skill records finished JTBDs by id and marks missing ones TBD; jobs-to-be-done owns minting them.
0 · bundle