dev-patterns
Skill0 starsChanged 22 days agoMITView on GitHub
House build patterns - auth/roles, payments (Razorpay/Stripe), webhooks, cron/jobs, file uploads, email/WhatsApp, audit log, multi-currency, API errors, LLM features. Use for "add auth", "add payments", "integrate <API>". NOT new-project setup (dev-kickoff) or agent orchestration (dev-agents).
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- GetStream/stream-chat-reacttheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- GetStream/stream-chat-react★ 844same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/setup-project-context/templates/CLAUDE.mdCLAUDE.md
- backend-architectureSkill
- build-review-loopSkill
- capability-intakeSkill
- competitor-market-analysisSkill
- context-auditSkill
- data-analysis-insightsSkill
- data-privacy-securitySkill
- dev-agentsSkill
- frontend-system-designSkill
- idea-validatorSkill
- intellectual-property-licensingSkill
- international-legal-researchSkill
- legal-document-drafterSkill
- llm-councilSkill
- make-slidesSkill
- password-authentication-securitySkill
- privacy-data-protection-lawSkill
- project-estimation-planningSkill
- project-startSkill
- rea-researchSkill
- requirements-business-analystSkill
- secrets-credential-managerSkill
- seo-tech-stackSkill
- setup-project-contextSkill
- shopify-ui-auditSkill
- site-incidentSkill
- sop-process-builderSkill
- task-dispatchSkill
- technical-feasibilitySkill
- tech-research-intelligenceSkill
- update-mdSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Read project CLAUDE.md + Docs map: stack, host (VPS/PM2 vs Vercel), ORM, auth lib, existing libs.
- Very specific: line 38
Keep the flow steps; swap code shape to the project's ORM, router, auth lib, naming (agent.md → Code Standards).
- Distinctive: line 48
Every protected page, route handler and server action guards itself.
- Very specific: line 51
No prod reset/drop/--accept-data-loss/--force-reset/DELETE without explicit OK + backup first.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dev Patterns
Task: $ARGUMENTS
House pattern library used mid-build: "how do we do X here". Pick → adapt → verify. Load only the reference(s) the task needs.
Index
| Need | Load |
| login, SSO, allowlist, roles/permissions, page guards, Shopify app OAuth, WP caps | references/auth-roles.md |
| checkout, gateway, order states, refunds, reconciliation, GST invoice | references/payments.md |
| inbound webhook, cron, queue, background job, retries, dead letters, rate limits | references/webhooks-jobs.md |
| DB access, migrations, audit log, soft delete, UTC/money storage, uploads (R2/S3), backups | references/data-files.md |
| transactional email, WhatsApp/SMS, OTP delivery, notifications, Payload hooks | references/messaging.md |
| route vs server action, response shape, zod, errors, external API clients, caching | references/api-errors.md |
| ₹ lakh/crore vs Western formats, timezones, locales, hreflang, phone/address, consent | references/i18n-markets.md |
| LLM feature inside a client app | references/ai-features.md |
Cross-cutting features load several: checkout = payments + webhooks-jobs + messaging + data-files.
Before picking
- Read project
CLAUDE.md+ Docs map: stack, host (VPS/PM2 vs Vercel), ORM, auth lib, existing libs. - Grep repo for an existing implementation (
lib/auth*,*mail*,cron,webhook,money,storage). Extend it; don't add a parallel one. - Sibling the agency project already solved it → copy the pattern only. Never its data, DB, creds or env values.
- Smallest pattern that meets the need. No adapter interface for one provider, no Redis/queue infra for 10 jobs/day.
- Stack fork: Next.js = default code shapes · WP/PHP + Shopify flagged per reference · other Node/PHP in Docker → adapt the Next shape.
Adapting
- Keep the flow steps; swap code shape to the project's ORM, router, auth lib, naming (
agent.md→ Code Standards). - Third-party accounts (gateway, SMTP, WhatsApp, Google Cloud, R2, LLM key) = client-owned, client email. Unknown → ask. the agency's own products exempt.
- Client code: client prefix or neutral names. No
org/the-orgin classes, IDs, files, comments. - Secrets: env var NAMES only in code, docs, chat. Values →
.envFILL_ME+ hidden-inputset-secrets.sh(read -rsp) the user runs on the target. (verify)= legal/tax/provider-limit claim. Confirm against current official docs (Context7 / provider docs) before shipping.- React UI for the feature → Astryx + Motion. Never in WP/PHP/Liquid.
Hard rules
- Server is source of truth: amount, price, role, status, ownership. Client input is a request, never a fact.
- Every protected page, route handler and server action guards itself. Middleware alone ≠ auth.
- Inbound events: verify + store + idempotent. Outbound calls: timeout + bounded retry.
- Store UTC. Money = integer minor units + currency code.
- No prod reset/drop/
--accept-data-loss/--force-reset/DELETE without explicit OK + backup first. - Code change →
build-review-loop. Push/merge/deploy/prod data writes → explicit approval. - Auth, payments, uploads, webhooks → focused
/security-auditpass before go-live.
Verify (every pattern)
- Name the end state first: "revoked user gets 401 on /orders", "webhook replayed 3× → 1 order, 1 email".
- Assert it on the real path (staging/live data, provider sandbox, headless browser with no cookies).
- Proxies are not proof: queue empty,
wp_mail()true, SMTPverify(), CI green,tscclean, "deploy success". - Indirect check → say it's indirect.
Point to, don't duplicate
- DB depth:
prisma-patterns,mysql-patterns,database-migrations(project-scoped) - LLM:
claude-api(provider/model/params) ·cost-aware-llm-pipeline(budgets/routing) - File-processing cache:
content-hash-cache-pattern - Vercel runtime:
vercel:queues,vercel:workflow,vercel:vercel-functions - Shopify Admin scripts:
<templates>/shopify-admin-appkit - Standards:
~/.claude/agent.md(Security, Response Shape, Error Handling, DB Safety, WP Rules)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

