Run the Claudinite generate-project-instructions skill against this repo and land its output.
Category (from evidence): a public, production-grade, solo-maintained monorepo that composes a client/UI browser-extension (MV3, no bundler) and a serverless backend (AWS SAM + Lambda + DynamoDB + CloudFront), joined by a shared drift-guarded single-source-of-truth. No single gallery label fits — it composes browser-extension + serverless-backend + monorepo.
Gap this closes: the working-instructions already exist but are distributed across the README, the component READMEs, dev/docs/architecture.md, dev/build/release/releasing.md, the dev/procedures/ lessons, and the auto-injected corpus packs. There is no single entry-point a fresh session/contributor reads to get productive (clean clone → run/see it work → verify → propose a change → conventions → handoff).
Change:
- Add
dev/procedures/working-instructions.md — lean and link-heavy per this repo's single-source-of-truth ethos; it restates the corpus working discipline nowhere and instead links where each rule already lives.
- Link it from the
dev/procedures/CLAUDE.md routing index.
Template-gap flag (for the owner): Claudinite has no templates/ directory, so this category has no matching playbook to base the doc on. The project-agnostic core of the new doc is the seed for a future .claudinite/templates/<category>.md — a separate, owner-approved step, not part of this change.
Also noticed (out of scope here — adopt-claudinite territory): this repo mounts Claudinite and layers lessons on the technology packs, but has no committed .claudinite-checks.json declaring those packs (chrome-extension, chrome-extension-release, aws-sam, node, github-actions, html), so the pack prose/checks may not be loading. Flagging for a follow-up.
Run the Claudinite
generate-project-instructionsskill against this repo and land its output.Category (from evidence): a public, production-grade, solo-maintained monorepo that composes a client/UI browser-extension (MV3, no bundler) and a serverless backend (AWS SAM + Lambda + DynamoDB + CloudFront), joined by a shared drift-guarded single-source-of-truth. No single gallery label fits — it composes browser-extension + serverless-backend + monorepo.
Gap this closes: the working-instructions already exist but are distributed across the README, the component READMEs,
dev/docs/architecture.md,dev/build/release/releasing.md, thedev/procedures/lessons, and the auto-injected corpus packs. There is no single entry-point a fresh session/contributor reads to get productive (clean clone → run/see it work → verify → propose a change → conventions → handoff).Change:
dev/procedures/working-instructions.md— lean and link-heavy per this repo's single-source-of-truth ethos; it restates the corpus working discipline nowhere and instead links where each rule already lives.dev/procedures/CLAUDE.mdrouting index.Template-gap flag (for the owner): Claudinite has no
templates/directory, so this category has no matching playbook to base the doc on. The project-agnostic core of the new doc is the seed for a future.claudinite/templates/<category>.md— a separate, owner-approved step, not part of this change.Also noticed (out of scope here —
adopt-claudiniteterritory): this repo mounts Claudinite and layers lessons on the technology packs, but has no committed.claudinite-checks.jsondeclaring those packs (chrome-extension,chrome-extension-release,aws-sam,node,github-actions,html), so the pack prose/checks may not be loading. Flagging for a follow-up.