Contracts
Thin core + domain sets for a fast, stack-aware project start. Cross-agent (Claude Code, Cursor, Codex, Gemini) via the SKILL.md standard. MIT.
npx -y skills add Neznakometz/StackForge --skill contractsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
The order for changing API contracts, DB schemas, and UI tokens. Apply for any change to DTOs, tables, or appearance.
SKILL.md
1.0 KB, as published. Nobody here has run it
Contracts
API / DTO:
- First the schema in a single place (single source of truth — e.g.
packages/shared), types are derived from the schema, not duplicated. - Then the server (request and response validation by the schema), then the client.
- Changed the schema — Grep over all usages, update all sides in a single commit.
DB:
- Only via migrations (drizzle-kit / Prisma / Alembic — depending on the stack), in the same PR as the code. Manual SQL in prod — not allowed.
- Multitenant tables must have a tenant/owner column + an index on it.
UI:
- Colors/spacing/radii — only design-system tokens. Before creating a component, check with
scoutwhether it already exists. - New UI strings — immediately into all i18n dictionaries.
LLM prompts (if any):
- Only separate files (
prompts/*.md), not strings in code; a prompt change — a separate commit (for rollback).