Conventions and guidelines for building prototypes and proof-of-concept projects — not for production use. Five skills: SPA frontends, Terraform/AWS infrastructure, Go and Node Lambdas, and product requirements. How a project records its own conventions, and the documentation, proposal, plan-of-action and glossary rules, are in the sibling documentation-and-planning plugin; general API design and MySQL conventions are in utils. Every skill is model-invoked on topic match; the plugin registers no hooks and adds no executable code.
5 skills
General-purpose utility commands, skills and agents for Claude Code, plus general conventions that are not specific to prototypes: api-design (HTTP/JSON URLs, payloads, list endpoints with filter[...], q and page-based pagination, 400 versus 422 errors, resource-suffix versioning) and mysql (schema naming, UUIDv7 keys, timestamps, migrations, SQL formatting, JSON operators and efficient index use). Includes the default-on auto-summary-commit workflow: a pair of hooks commits the prompt and its summary at the end of every turn that changed files, scoped to the paths that turn actually changed.
3 skills · 1 command · hooks
Four skills carrying the portable layer of documentation and planning conventions: conventions (how a project records its own rules in conventions/, the two-layer model, and precedence), documentation (the markdown rules every document follows, including an up-to-date table of contents; the three tenses of architecture/, instructions/ and proposals/; API docs, READMEs, diagrams and writing proposals, with their decisions and assumption tests in files of their own), plan-of-action (the staged implementation plan a settled proposal becomes, and carrying it out stage by stage), and glossary (one file per term, linked rather than restated). Model-invoked on topic match; the plugin registers no hooks and adds no executable code.
4 skills
Engineering conventions for projects built to run in production — the counterpart to prototype-conventions. Three skills so far. Terraform and AWS infrastructure — shared remote state (GitLab-managed, HCP Terraform, S3 or another backend) with CI-only applies of a reviewed plan, tagging and environment-aware resource naming, Lambda timeouts and configuration, Lambda code deployed by CI behind a live alias, protecting stateful resources, Aurora with Secrets Manager, S3/CloudFront hosting deployed by CI, Route 53/SES with DMARC, Cognito and WAF. Go and Node.js AWS Lambdas — trigger-based directory naming, module and package layout, structured JSON logging (slog, Powertools), failure handling (context deadlines, idempotency, partial batch failures, dead-letter queues), OpenTelemetry metrics over OTLP to CloudWatch for CloudWatch Omni, tracing and alarms, CI-built reproducible arm64 artifacts and go.work, govulncheck and npm audit, and unit plus integration testing. Model-invoked on topic match; the plugin registers no hooks and adds no executable code.
3 skills