Standards for code that ships
20 ways in, from Security to System Design — every standard links back to the package and the model families that ship it.
304 packages · 20 categories
airbnb
A warm, generous consumer marketplace anchored on a clean white canvas and Airbnb Rausch (#ff385c), the single brand voltage that carries every…
airtable
A sober, editorial workflow-software interface anchored on white canvas and dark-ink type, where brand voltage comes from full-bleed signature cards…
apple
A photography-first interface that turns marketing into a museum gallery, updated for Apple's 2026 Liquid Glass design language. Edge-to-edge product…
binance
A confident financial-platform interface anchored on a deep near-black canvas, where Binance's iconic yellow (#FCD535) carries every primary CTA,…
bmw
BMW's corporate site — distinct from BMW M's motorsport-bombastic variant, this is a measured and settled corporate-automotive interface. On a light…
bmw-m
A motorsport-engineering interface anchored on a near-black canvas with white BMW Type Next Latin display headlines in confident UPPERCASE. The brand…
authentication
Wiring authentication into a backend service — session versus token, the verification middleware, refresh and rotation, and multi-tenant identity.
authorization
Enforcing access control in a service — where the check belongs, scoping queries by tenant, RBAC versus ABAC, and testing that a denial is actually…
background-jobs
Running work outside the request — job design, scheduling, idempotency, timeouts, observability, and the failure modes of cron in a distributed…
django
Django project structure — app boundaries, models and migration discipline, queryset hygiene that avoids N+1, forms and serializers, split settings,…
Sending transactional email that arrives — SPF/DKIM/DMARC, provider choice, templating, bounce handling, and keeping the sending domain reputable.
error-handling
Error handling in a server — the boundary that converts failures to responses, typed domain errors, retries, and what must never reach the client.
audit-log
Recording security-relevant events so a breach is detectable — what to log, what never to log, and making the record tamper-evident.
authentication
Password storage, session handling and login-flow rules for building authentication that survives a credential-stuffing campaign and a database leak.
authorization
Deciding what an authenticated user may do — enforcing at the data layer, preventing IDOR, and modelling roles without permission sprawl.
command-injection
Executing external programs without letting input become part of the command — argument arrays, why shells are the problem, and safe temporary files.
cors
Configuring cross-origin resource sharing without opening your API — explicit origins, why reflection is dangerous, and what CORS does not protect.
csrf
Preventing cross-site request forgery with SameSite cookies, synchroniser tokens, and Origin validation — and knowing which one is actually…
client-components
Client components — when interactivity justifies the bundle, hydration correctness, browser-API access, and keeping the boundary small.
code-splitting
Splitting the bundle so users download only what they need — route and component boundaries, prefetching on intent, and avoiding waterfalls.
folder-structure
Organising a frontend codebase — colocation by feature, import boundaries enforced by tooling, naming, and the shared layer that becomes a dumping…
forms
Forms that are accessible, resilient and correct — controlled state, validation timing, submission and error handling, and never trusting the client.
hooks
React hooks — the rules that make them work, dependency correctness, custom hook design, and the ones that replace an effect entirely.
hydration
Hydration correctness — why server and client HTML must match, the values that reliably break it, and how to handle genuinely client-only content.
architecture
This document defines engineering principles, architectural methodologies, system design frameworks, organizational practices, and long-term…
caching
This document defines engineering principles, caching methodologies, data reuse strategies, latency reduction practices, workload optimization…
cdn
This document defines engineering principles, Content Delivery Network (CDN) methodologies, edge delivery strategies, content distribution practices,…
clean-architecture
This document defines engineering principles, dependency management methodologies, architectural boundary design, system organization practices, and…
ddd
This document defines engineering principles, domain modeling methodologies, business knowledge organization, strategic design practices, and…
distributed-systems
This document defines engineering principles, distributed systems methodologies, communication strategies, consistency models, fault tolerance…
backup
Backups that actually restore — point-in-time recovery, retention, encryption, and the restore drill that is the only proof a backup exists.
go-database
Database access from Go — database/sql and pgx, pool sizing, transactions that always resolve, sqlc versus ORMs, migrations, scanning, and context…
indexes
Indexing for real query patterns — column order in composite indexes, when an index is ignored, and the cost of the ones you do not need.
migration
Schema changes that deploy without downtime — expand-contract, locks that block writes, and backfilling large tables safely.
mongodb
MongoDB document modelling and operational rules — embed versus reference, indexes, write concern, transactions, and the failure modes of a…
mysql
MySQL and MariaDB specifics — InnoDB, charset and collation, gap locks, online DDL, and the defaults that silently corrupt data.
aws
Running on AWS safely — IAM least privilege, network layout, encryption defaults, cost control, and the misconfigurations that cause breaches and…
backups
Backing up infrastructure and state — what is actually stateful, immutability against ransomware, cross-account isolation, and restore drills.
cicd
Pipelines that catch real problems fast — stage ordering, caching, build-once promotion, secrets handling, and gates that are worth blocking a merge…
cloudflare
Cloudflare as CDN, WAF and edge platform — DNS and proxying, cache rules that actually cache, origin protection, Workers limits, and rate limiting.
deployment
Shipping without downtime — rolling, blue/green and canary strategies, graceful shutdown, backward-compatible changes, and verifying before declaring…
disaster-recovery
Planning and rehearsing recovery from a major failure — RTO and RPO, failure scenarios, runbooks, incident roles, and drills that find the gaps.
budgets
Performance budgets as a CI contract — p50/p95 latency and RSS caps per scenario, a reproducible benchmark script, a committed baseline, and a…
bundle-size
Keeping JavaScript small — measuring before cutting, dependency discipline, tree shaking that actually works, and budgets enforced in CI.
caching
Caching layers, invalidation strategies, stampede protection and the correctness rules that keep a cache from serving one user another user's data.
cpu
CPU-bound work — profiling with flame graphs, algorithmic complexity, keeping event loops free, parallelism, and knowing when CPU is not the problem.
database
Database performance at the system level — connection pooling, saturation, lock contention, bloat, and the signals that tell you which one you have.
fonts
Web font delivery — self-hosting, subsetting, font-display, metric-compatible fallbacks, and eliminating the layout shift a font swap causes.
architecture-analysis
This document defines engineering principles, systematic architectural evaluation methods, system decomposition techniques, dependency analysis…
compatibility
This document defines engineering principles, compatibility evaluation methodologies, interoperability strategies, interface stability practices,…
dependency-analysis
This document defines engineering principles, dependency evaluation methods, relationship analysis techniques, architectural assessment standards,…
ecosystem-building
This document defines engineering principles, ecosystem development methodologies, community-centered architecture strategies, governance models,…
enhancement
This document defines engineering principles, capability expansion strategies, architectural enhancement methods, feature evolution practices,…
fork-strategy
This document defines engineering principles, decision frameworks, repository divergence strategies, synchronization models, governance practices,…
agent-rules
This document defines the behavioral operating rules for Claude during software engineering tasks.
context
This document defines how context should be collected, maintained, expanded, and utilized throughout an engineering session.
hallucination
This document defines the anti-hallucination engineering protocol.
memory
This document defines how memory should be managed during engineering tasks.
multi-agent
This document defines how complex engineering tasks should be decomposed into multiple specialized reasoning roles.
optimization
This document defines the engineering optimization methodology.
accessibility
Testing for accessibility — what automation catches, what it cannot, and the keyboard and screen-reader checks that find real barriers.
e2e
End-to-end tests that are worth their cost — user-visible selectors, deterministic waiting, and keeping the suite small enough to trust.
go-testing
Testing in Go with the standard toolchain — table-driven subtests, t.Helper, httptest and fstest, golden files, benchmarks, the race detector,…
integration
Testing across real boundaries — real databases in containers, isolation between tests, and faking third parties without faking their behaviour.
load
Load testing that predicts production behaviour — modelling real traffic, measuring percentiles not averages, and finding the knee before users do.
performance
Testing performance as a regression gate — budgets in CI, lab versus field data, and measuring the metrics users actually feel.
api-security
Securing an HTTP API — authentication at the edge, per-object authorization, input validation, transport, and the controls that stop the OWASP API…
filtering
Filter parameters that are expressive without being injectable — allowlisted fields, typed operators, index-backed queries, and bounded cost.
graphql
GraphQL schema and server rules — bounding query cost, killing N+1 with dataloaders, per-field authorization, and errors clients can act on.
open-api
OpenAPI specifications that stay true — generating from code, gating breaking changes in CI, and producing docs and SDKs from one source.
pagination
Cursor and offset pagination — which to use, how to encode a cursor, and why deep OFFSET pages get slower and skip rows.
rate-limiting
Rate limiting that protects the service without punishing legitimate clients — algorithm choice, key selection, headers, and distributed enforcement.
analytics
This document defines how Claude should design, evaluate, optimize, and continuously improve analytics systems for SaaS platforms, AI applications,…
branding
This document defines how Claude should design, evaluate, refine, and maintain world-class product and company branding.
competitor-analysis
This document defines how Claude should perform comprehensive competitor analysis for products, startups, SaaS platforms, APIs, developer tools, AI…
content
This document defines how Claude should design, evaluate, optimize, and continuously improve content strategies for SaaS products, AI applications,…
growth
This document defines how Claude should design, evaluate, optimize, and continuously improve sustainable product growth strategies for SaaS…
marketing
This document defines how Claude should design, evaluate, optimize, and continuously improve marketing strategies for products, SaaS platforms, AI…
deployment-checklist
This checklist defines the minimum operational requirements for deploying software safely, consistently, and predictably into production environments.
design-checklist
This checklist defines the minimum design requirements for software products before implementation, release, or production approval.
launch-checklist
This checklist defines the minimum requirements for successfully launching a software product, feature, platform, API, AI application, SaaS product,…
performance-checklist
This checklist defines the minimum performance requirements for software systems before production deployment, feature release, or major…
production-checklist
This checklist defines the minimum quality requirements for declaring any software system production ready.
qa-checklist
This checklist defines the minimum Quality Assurance (QA) requirements before any software product, feature, API, AI application, or platform is…
accessibility-review
This document defines the Accessibility Review methodology.
architecture-review
This document defines the Architecture Review methodology for software engineering.
code-review
This document defines the professional code review methodology for engineering tasks.
design-review
This document defines the Design Review methodology for modern digital products.
performance-review
This document defines the Performance Review methodology for software engineering.
product-review
This document defines the Product Review methodology.
customer-feedback
This document defines engineering principles, customer feedback methodologies, learning frameworks, evidence evaluation strategies, organizational…
fundraising
This document defines engineering principles, fundraising methodologies, investment readiness frameworks, company evaluation strategies, governance…
launch
This document defines engineering principles, product launch methodologies, release strategies, operational readiness frameworks, customer adoption…
mvp
This document defines how to scope, build, and ship a minimum viable product: what belongs in a first release, what does not, and how to tell the…
product-market-fit
This document defines engineering principles, product-market fit methodologies, customer alignment frameworks, sustainable growth strategies,…
retention
This document defines engineering principles, customer retention methodologies, engagement frameworks, long-term value strategies, operational…
ai-template
This template provides complete engineering context for designing production-ready Artificial Intelligence products that solve real business problems…
blockchain-template
This template provides complete engineering context for designing production-ready blockchain applications that solve real business problems through…
dashboard-template
This template provides a complete engineering context for designing modern dashboards that transform complex business data into actionable insights…
landing-template
This template provides a complete engineering context for designing world-class product landing pages that communicate value, establish trust,…
marketplace-template
This template provides complete engineering context for designing production-ready digital marketplaces that efficiently connect buyers and sellers,…
portfolio-template
This template provides complete engineering context for designing world-class personal, developer, designer, founder, agency, and professional…
api-docs
This document defines engineering principles, architectural guidance, documentation standards, operational expectations, and best practices for…
architecture-docs
This document defines engineering principles, architectural standards, documentation practices, and long-term governance for creating Architecture…
changelog
This document defines engineering principles, documentation standards, governance practices, and operational expectations for maintaining…
contributing
This document defines engineering principles, contribution standards, collaboration workflows, review expectations, and quality requirements for…
readme
This repository is a structured engineering knowledge base designed to standardize how modern software systems are designed, implemented, reviewed,…
style-guide
This document defines engineering writing standards, documentation conventions, terminology rules, formatting principles, and structural guidelines…
code-of-conduct
This Code of Conduct defines the expected standards of behavior for everyone participating in this repository and its community.
contributing
This document defines the contribution standards, expectations, workflows, and review process for everyone contributing to this repository.
governance
This document defines the governance model used to guide the long-term growth, decision-making, quality standards, ownership, and sustainability of…
maintainers
This document defines what it means to be a maintainer of a repository: what maintainers are responsible for, how people become maintainers, how they…
preset-guidelines
This document defines how reusable instruction presets should be designed, evaluated, maintained, and continuously improved for AI-assisted…
benchmark
This document defines engineering principles, benchmarking methodologies, performance evaluation frameworks, measurement standards, comparative…
case-studies
This document defines engineering principles, case study methodologies, analytical frameworks, evidence evaluation standards, decision analysis…
competitor-research
This document defines engineering principles, competitive analysis methodologies, product evaluation frameworks, market positioning strategies,…
technology-trends
This document defines engineering principles, technology trend analysis methodologies, innovation evaluation frameworks, adoption strategies, risk…
ui-analysis
This document defines engineering principles, analytical methodologies, evaluation frameworks, usability standards, visual hierarchy guidelines,…