claude

Engineering Conventions

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.

0 on GitHubby Stefan Hornerv0.7.0MITupdated todayproductivity
/

Plugin engineering-conventions from marketplace stefs-plugins in tedslittlerobot/stefs-claude-plugins. Commands read from the repo's manifest — today.

What it installs

Skills (3)

  • infrastructure

    Terraform and AWS conventions for production — never running apply (CI applies a reviewed plan), shared remote state (GitLab-managed Terraform state, HCP Terraform / Terraform Cloud in local execution mode, an S3 backend with use_lockfile, or another backend), per-environment tfvars and state per en

  • lambdas-go

    Go AWS Lambda conventions for production — directory naming by trigger (api-<method>-, api-socket-, alb-<method>-, url-, sqs-, sns-, mq-, dynamo-, kinesis-, kafka-, docdb-, s3-, bus-, pipe-, schedule-, cognito-, logs-, alarm-, email-, iot-, aurora-, lambda-, secrets-, invoke-) for API Gateway, WebSo

  • lambdas-node

    Node.js AWS Lambda conventions for production — when Node is justified over Go, ESM/.mjs modules, the nodejs runtime on arm64 and index.handler entry point, bundling with esbuild and npm ci in CI, factory-function dependency injection, structured JSON logging with Powertools for AWS Lambda Logger an

View source on GitHub

More from tedslittlerobot/stefs-claude-plugins

All 4 plugins →

Prototype Conventions

claude

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

0

Utils

claude

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

0

Documentation and Planning

claude

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

0

Similar plugins

mattpocock-skills

claude

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

caveman

claude

Talk like caveman. Cut filler. Keep technical details explicit.

22 skills · 1 command · 3 agents · hooks

JuliusBrussee/caveman 119,462

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

Taste Skill

claudecodex

tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.

1 skill

Leonxlnx/taste-skill 114,391

career-ops

claudecodex

Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications

5 skills · hooks

career-ops-hq/career-ops 82,253

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

Maintain Engineering Conventions?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins4 plugins