@zigrivers/scaffold 3.33.5 → 3.33.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1 +1 @@
1
- 0.1.10
1
+ 0.1.14
@@ -1,13 +1,26 @@
1
1
  ---
2
2
  name: browser-extension-store-submission
3
- description: Chrome Web Store review process, AMO submission, screenshot and promotional image requirements, listing optimization, and managing version updates
4
- topics: [browser-extension, store-submission, chrome-web-store, amo, listing-optimization, review-process, screenshots]
3
+ description: >-
4
+ Chrome Web Store review process, AMO submission, screenshot and promotional image requirements, listing optimization,
5
+ and managing version updates
6
+ topics:
7
+ - browser-extension
8
+ - store-submission
9
+ - chrome-web-store
10
+ - amo
11
+ - listing-optimization
12
+ - review-process
13
+ - screenshots
5
14
  volatility: evolving
6
- last-reviewed: null
15
+ last-reviewed: 2026-06-07
7
16
  version-pin: null
8
17
  sources:
9
18
  - url: https://developer.chrome.com/docs/webstore/publish
19
+ hash: sha256:c81bca9d736a2ad631c41f1c4f484b6341afcbd5cd5e5ea6d1dbccf909c04511
20
+ retrieved: 2026-06-07
10
21
  - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Distribution
22
+ hash: sha256:36cf6edeaf11509b684bdf7b21d78cb5fe0330697a34acff91903d70d33430e7
23
+ retrieved: 2026-06-07
11
24
  ---
12
25
 
13
26
  Store submission is the deployment step for browser extensions. Unlike web applications where you push to a server, extensions must pass store review before reaching users. Review timelines, policy requirements, and listing quality directly affect user acquisition and approval success. Understanding the process before writing the first line of code prevents costly late-stage pivots.
@@ -1,13 +1,27 @@
1
1
  ---
2
2
  name: browser-extension-testing
3
- description: Extension testing with Puppeteer and Playwright, unit testing shared logic, and manual cross-browser smoke test procedures
4
- topics: [browser-extension, testing, puppeteer, playwright, unit-testing, e2e, smoke-tests, cross-browser]
3
+ description: >-
4
+ Extension testing with Puppeteer and Playwright, unit testing shared logic, and manual cross-browser smoke test
5
+ procedures
6
+ topics:
7
+ - browser-extension
8
+ - testing
9
+ - puppeteer
10
+ - playwright
11
+ - unit-testing
12
+ - e2e
13
+ - smoke-tests
14
+ - cross-browser
5
15
  volatility: evolving
6
- last-reviewed: null
16
+ last-reviewed: 2026-06-07
7
17
  version-pin: null
8
18
  sources:
9
19
  - url: https://developer.chrome.com/docs/extensions/how-to/test/end-to-end-testing
20
+ hash: sha256:66bf76a65993daa9fcb0daba148e6780cd54d34a0fd013c24634ed86f4115e4f
21
+ retrieved: 2026-06-07
10
22
  - url: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Testing_persistent_and_restart_features
23
+ hash: sha256:ca07150330ba40d75080deedf3928e78776615c6fdab4ad83de7999c17890ee8
24
+ retrieved: 2026-06-07
11
25
  ---
12
26
 
13
27
  Browser extension testing is harder than web app testing because the extension runs in a privileged browser context that most test frameworks cannot easily access. The strategy is to maximize the code that lives in plain TypeScript (easily unit-tested), minimize the code that requires a real browser to test (expensive), and write targeted end-to-end tests that exercise the extension in a real browser for the scenarios that matter most.
@@ -1,12 +1,23 @@
1
1
  ---
2
2
  name: cli-dev-environment
3
- description: Local development setup for CLIs including npm link, cargo install, debug flags, manual testing workflow, and hot reload
4
- topics: [cli, dev-environment, npm-link, cargo, debug, hot-reload, testing-workflow]
3
+ description: >-
4
+ Local development setup for CLIs including npm link, cargo install, debug flags, manual testing workflow, and hot
5
+ reload
6
+ topics:
7
+ - cli
8
+ - dev-environment
9
+ - npm-link
10
+ - cargo
11
+ - debug
12
+ - hot-reload
13
+ - testing-workflow
5
14
  volatility: evolving
6
- last-reviewed: null
15
+ last-reviewed: 2026-06-07
7
16
  version-pin: null
8
17
  sources:
9
18
  - url: https://docs.astral.sh/uv/
19
+ hash: sha256:81d5796b079a3cd0448a2a99ffd23bcd684922c52c36f8c8ecf212804da271e2
20
+ retrieved: 2026-06-07
10
21
  ---
11
22
 
12
23
  CLI development has a tighter feedback loop requirement than library development: you need to run the actual binary, observe its output, and verify behavior against real filesystem and network state. Setting up a fast local development workflow is not optional — a slow iteration cycle compounds across hundreds of test invocations.
@@ -1,12 +1,25 @@
1
1
  ---
2
2
  name: cli-distribution-patterns
3
- description: npm, pip, and cargo publishing, Homebrew formulae, standalone binaries, Docker images, and GitHub Releases with checksums
4
- topics: [cli, distribution, npm, homebrew, cargo, pip, standalone-binaries, github-releases, checksums]
3
+ description: >-
4
+ npm, pip, and cargo publishing, Homebrew formulae, standalone binaries, Docker images, and GitHub Releases with
5
+ checksums
6
+ topics:
7
+ - cli
8
+ - distribution
9
+ - npm
10
+ - homebrew
11
+ - cargo
12
+ - pip
13
+ - standalone-binaries
14
+ - github-releases
15
+ - checksums
5
16
  volatility: evolving
6
- last-reviewed: null
17
+ last-reviewed: 2026-06-07
7
18
  version-pin: null
8
19
  sources:
9
20
  - url: https://peps.python.org/pep-0621/
21
+ hash: sha256:7a37a1354520a9a9f31ff547e6318d8f06fbf3c02c435caf41d3cb9306989995
22
+ retrieved: 2026-06-07
10
23
  ---
11
24
 
12
25
  Distribution is where many CLI projects fail: the tool works perfectly in development but is painful to install, update, or run in different environments. A well-distributed CLI reaches users through multiple channels (package manager, direct download, container) and handles updates gracefully.
@@ -1,15 +1,24 @@
1
1
  ---
2
2
  name: adr-craft
3
3
  description: Writing effective architecture decision records including technology selection
4
- topics: [adr, architecture-decisions, tech-stack, decision-documentation, technology-selection]
4
+ topics:
5
+ - adr
6
+ - architecture-decisions
7
+ - tech-stack
8
+ - decision-documentation
9
+ - technology-selection
5
10
  volatility: stable
6
- last-reviewed: null
11
+ last-reviewed: 2026-06-07
7
12
  version-pin: null
8
13
  sources:
9
14
  - url: https://adr.github.io/
10
15
  anchor: '#decision-record-templates'
16
+ hash: sha256:56c48fcbfa504a3b058d57058dd6dfbab83fc879bc405317d847ec5a2efbd2b6
17
+ retrieved: 2026-06-07
11
18
  - url: https://github.com/joelparkerhenderson/architecture-decision-record
12
19
  anchor: '#adr-templates'
20
+ hash: sha256:0155a98859571e056061d2205db0bf1a7088ee91d6681d85a98f7401d0a6a962
21
+ retrieved: 2026-06-07
13
22
  ---
14
23
 
15
24
  ## Summary
@@ -1,13 +1,29 @@
1
1
  ---
2
2
  name: ai-memory-management
3
- description: AI memory and context management patterns for Claude Code projects including modular rules, MCP memory servers, lifecycle hooks, decision logging, and external context integration
4
- topics: [ai-memory, claude-code, claude-rules, mcp-servers, lifecycle-hooks, context-management, session-handoff, decision-logging, mcp-knowledge-graph, context7]
3
+ description: >-
4
+ AI memory and context management patterns for Claude Code projects including modular rules, MCP memory servers,
5
+ lifecycle hooks, decision logging, and external context integration
6
+ topics:
7
+ - ai-memory
8
+ - claude-code
9
+ - claude-rules
10
+ - mcp-servers
11
+ - lifecycle-hooks
12
+ - context-management
13
+ - session-handoff
14
+ - decision-logging
15
+ - mcp-knowledge-graph
16
+ - context7
5
17
  volatility: fast-moving
6
- last-reviewed: null
18
+ last-reviewed: 2026-06-07
7
19
  version-pin: null
8
20
  sources:
9
21
  - url: https://modelcontextprotocol.io/specification
22
+ hash: sha256:ebe289f5f9ad3d8fd9eb09105a74bff6f5efdfc4cd383759f6f82cf57f3ba724
23
+ retrieved: 2026-06-07
10
24
  - url: https://docs.anthropic.com/en/docs/build-with-claude/memory
25
+ hash: sha256:e246d2cd069bcb9c7b78d437ffc1672ce45d6ae2393571c00d436e9f7e494f0f
26
+ retrieved: 2026-06-07
11
27
  ---
12
28
 
13
29
  # AI Memory Management
@@ -111,6 +127,163 @@ This replaces inline convention blocks, keeping CLAUDE.md under 200 lines (the e
111
127
 
112
128
  #### MCP Memory Servers
113
129
 
130
+ The Model Context Protocol (MCP) specification (https://modelcontextprotocol.io/specification) defines the protocol for servers that provide context and capabilities to LLM applications. The specification covers server features including Resources, Prompts, and Tools, but does not prescribe specific MCP server implementations.
131
+
132
+ **Configuration pattern** (`.claude/settings.json`):
133
+ ```json
134
+ {
135
+ "mcpServers": {
136
+ "memory": {
137
+ "command": "npx",
138
+ "args": ["-y", "@modelcontextprotocol/server-memory"],
139
+ "env": {
140
+ "MEMORY_FILE_PATH": ".claude/memory-graph.json"
141
+ }
142
+ }
143
+ }
144
+ }
145
+ ```
146
+
147
+ #### Lifecycle Hooks
148
+
149
+ Hooks automate memory capture at key session events:
150
+
151
+ **PreCompact** (highest value) — Triggers before context compression. Logs when compaction occurs for debugging context loss.
152
+
153
+ ```json
154
+ {
155
+ "hooks": {
156
+ "PreCompact": [{
157
+ "type": "command",
158
+ "command": "echo \"$(date '+%Y-%m-%d %H:%M:%S') — Context compacting\" >> .claude/compaction-log.txt",
159
+ "timeout": 5000
160
+ }]
161
+ }
162
+ }
163
+ ```
164
+
165
+ File-logging for compaction events:
166
+ ```json
167
+ {
168
+ "hooks": {
169
+ "PreCompact": [{
170
+ "type": "command",
171
+ "command": "date '+%Y-%m-%d %H:%M' >> .claude/compaction-log.txt && echo 'Context compacted' >> .claude/compaction-log.txt",
172
+ "timeout": 5000
173
+ }]
174
+ }
175
+ }
176
+ ```
177
+
178
+ **Stop** — Triggers when a session ends. Good for capturing session-level summaries.
179
+
180
+ **PreToolUse** — Triggers before tool calls. Can log decisions about file modifications. Use sparingly — high frequency means high overhead.
181
+
182
+ **Hook selection guidance:**
183
+ - Start with PreCompact only — it captures the most value with least noise
184
+ - Hook commands must produce a side effect (write to MCP server, append to file) — echoing to `/dev/null` provides zero value
185
+ - Add Stop if sessions frequently end with unrecorded decisions
186
+ - Avoid PreToolUse unless you have a specific logging need — it fires constantly
187
+
188
+ #### Decision Logging
189
+
190
+ Decisions are the highest-value memory type because they cannot be derived from code. A decision log captures what was chosen, what was rejected, and why.
191
+
192
+ **Structure:**
193
+ ```
194
+ docs/decisions/
195
+ DECISIONS.md # Index of all decisions
196
+ 001-auth-strategy.md # Individual decision records
197
+ 002-database-choice.md
198
+ ```
199
+
200
+ **Decision entry format:**
201
+ ```markdown
202
+ ## DEC-001: JWT over session cookies for auth
203
+
204
+ **Date:** 2026-03-27
205
+ **Context:** Need stateless auth for API-first architecture
206
+ **Decision:** Use JWT with short-lived access tokens + refresh tokens
207
+ **Rejected:** Session cookies (requires sticky sessions), OAuth-only (too complex for MVP)
208
+ **Consequences:** Need token refresh logic in frontend, need secure token storage
209
+ ```
210
+
211
+ This complements ADRs (which cover architecture-level decisions) by capturing day-to-day implementation decisions that would otherwise be lost between sessions.
212
+
213
+ #### Session Handoff Patterns
214
+
215
+ When context hits limits, structured handoff preserves continuity:
216
+
217
+ 1. **Before compaction**: Save current task state, open questions, and recent decisions
218
+ 2. **After compaction**: Claude Code auto-reloads CLAUDE.md and auto-memory, but loses working context
219
+ 3. **Recovery**: Agent reads decision log and memory server to reconstruct working state
220
+
221
+ The `/compact` command is the natural handoff point. A PreCompact hook that saves session state ensures nothing critical is lost.
222
+
223
+ ### Tier 3: External Context
224
+
225
+ #### Library Documentation Servers
226
+
227
+ AI agents hallucinate APIs — they generate plausible but incorrect function signatures, especially for rapidly-evolving libraries. External doc servers solve this by providing current, version-specific documentation on demand.
228
+
229
+ **Context7** (by Upstash) — Most popular, fetches current library docs via MCP
230
+ - Covers major frameworks (React, Next.js, Vue, Angular, etc.)
231
+ - Free tier: 1,000 requests/month
232
+ - Caution: had a security vulnerability (patched) — review before enabling
233
+
234
+ **Nia** (by Nozomio) — Indexes codebases + 3,000+ pre-indexed packages
235
+ - Cross-session context persistence
236
+ - Deep research agent for complex questions
237
+ - Y Combinator backed, more comprehensive than Context7
238
+
239
+ **Docfork** — 9,000+ libraries, MIT license
240
+ - "Cabinets" for project-specific documentation isolation
241
+ - Self-hostable
242
+
243
+ **Configuration pattern:**
244
+ ```json
245
+ {
246
+ "mcpServers": {
247
+ "context7": {
248
+ "command": "npx",
249
+ "args": ["-y", "@upstash/context7-mcp@latest"]
250
+ }
251
+ }
252
+ }
253
+ ```
254
+
255
+ **When to enable:** Projects with 3+ external dependencies, especially rapidly-evolving frameworks (React, Next.js, Svelte). Skip for standard library-only projects or well-established stable APIs.
256
+
257
+ ### Anti-Patterns
258
+
259
+ | Anti-Pattern | Why It Fails | Instead |
260
+ |-------------|-------------|---------|
261
+ | Dumping entire codebase into context | Drowns signal in noise, costs tokens | Let the agent read files on demand |
262
+ | Storing code patterns in memory | Duplicates what's in the code; goes stale | Store decisions and rationale only |
263
+ | Huge CLAUDE.md (500+ lines) | Adherence drops sharply above 200 lines | Use .claude/rules/ for specifics |
264
+ | Memory without structure | Unstructured notes become unsearchable noise | Use categories (decision, lesson, error) |
265
+ | Capturing everything | Token cost with diminishing returns | Capture what can't be derived from code |
266
+ | Multiple overlapping memory tools | Conflicting context, duplicated entries | Pick one MCP server, use it consistently |
267
+
268
+ ### Integration with Beads
269
+
270
+ When Beads is configured, memory complements task tracking:
271
+ - **Beads** tracks what work to do (tasks, dependencies, status)
272
+ - **Memory** tracks how to do work better (patterns, decisions, lessons)
273
+ - Decision log entries can reference Beads task IDs for traceability
274
+ - `tasks/lessons.md` remains the cross-session learning file; MCP memory adds structured queryability
275
+ - Don't duplicate: if a pattern is in `tasks/lessons.md`, don't also store it in the MCP server
276
+
277
+ ## Coding Conventions
278
+ See `docs/coding-standards.md` for full reference. Key rules in `.claude/rules/code-style.md`.
279
+ ```
280
+
281
+ This replaces inline convention blocks, keeping CLAUDE.md under 200 lines (the empirically-validated adherence threshold).
282
+
283
+ ### Tier 2: Persistent Memory
284
+
285
+ #### MCP Memory Servers
286
+
114
287
  **Recommended: MCP Knowledge Graph** (`@modelcontextprotocol/server-memory`)
115
288
  - Official MCP server from the Model Context Protocol project
116
289
  - Stores entities, relations, and observations in a local JSON file
@@ -1,13 +1,25 @@
1
1
  ---
2
2
  name: api-design
3
3
  description: API design principles for REST, GraphQL, and inter-service communication
4
- topics: [api, rest, graphql, endpoints, contracts, versioning, error-handling, authentication]
4
+ topics:
5
+ - api
6
+ - rest
7
+ - graphql
8
+ - endpoints
9
+ - contracts
10
+ - versioning
11
+ - error-handling
12
+ - authentication
5
13
  volatility: evolving
6
- last-reviewed: null
7
- version-pin: 'OpenAPI 3.1 / GraphQL October 2021'
14
+ last-reviewed: 2026-06-07
15
+ version-pin: OpenAPI 3.1 / GraphQL October 2021
8
16
  sources:
9
17
  - url: https://spec.openapis.org/oas/v3.1.0
18
+ hash: sha256:ca07378639431519731065e397fa4170c2ddfe501a4aa69db60d6a3a9bb669fe
19
+ retrieved: 2026-06-07
10
20
  - url: https://spec.graphql.org/October2021/
21
+ hash: sha256:4f556e7bc74ffcdf6ba3c6a4d1f541bd736492db47e97349200a8dfcb80e0ad1
22
+ retrieved: 2026-06-07
11
23
  ---
12
24
 
13
25
  ## Summary
@@ -1,15 +1,31 @@
1
1
  ---
2
2
  name: automated-review-tooling
3
- description: Patterns for automated code review using AI CLI tools (Codex, Gemini, Claude) — three-CLI MMR orchestration plus Superpowers 4th channel in wrappers, reconciliation, compensating passes, PR + non-PR targets, and CI integration
4
- topics: [code-review, automation, codex, gemini, claude, pull-requests, non-pr-review, mmr, ci-cd, review-tooling]
3
+ description: >-
4
+ Patterns for automated code review using AI CLI tools (Codex, Gemini, Claude) — three-CLI MMR orchestration plus
5
+ Superpowers 4th channel in wrappers, reconciliation, compensating passes, PR + non-PR targets, and CI integration
6
+ topics:
7
+ - code-review
8
+ - automation
9
+ - codex
10
+ - gemini
11
+ - claude
12
+ - pull-requests
13
+ - non-pr-review
14
+ - mmr
15
+ - ci-cd
16
+ - review-tooling
5
17
  volatility: fast-moving
6
- last-reviewed: null
18
+ last-reviewed: 2026-06-07
7
19
  version-pin: null
8
20
  sources:
9
21
  - url: https://docs.anthropic.com/en/docs/claude-code/overview
10
22
  anchor: '#claude-code-cli'
23
+ hash: sha256:0436534c3261c036f500f0497ade28c8063f46533e780cd7d4d76821e79d062c
24
+ retrieved: 2026-06-07
11
25
  - url: https://ai.google.dev/gemini-api/docs
12
26
  anchor: '#cli-tools'
27
+ hash: sha256:7b940f480b27022e4cd3394c125a0173e3d9c79b4e650ab5bea51355049592cc
28
+ retrieved: 2026-06-07
13
29
  ---
14
30
 
15
31
  # Automated Review Tooling
@@ -1,15 +1,26 @@
1
1
  ---
2
2
  name: claude-md-patterns
3
- description: Patterns for structuring CLAUDE.md files including section organization, rule authoring, pointer patterns, and merge strategies
4
- topics: [claude-md, ai-configuration, rule-files, memory-management, project-setup]
3
+ description: >-
4
+ Patterns for structuring CLAUDE.md files including section organization, rule authoring, pointer patterns, and merge
5
+ strategies
6
+ topics:
7
+ - claude-md
8
+ - ai-configuration
9
+ - rule-files
10
+ - memory-management
11
+ - project-setup
5
12
  volatility: fast-moving
6
- last-reviewed: null
13
+ last-reviewed: 2026-06-07
7
14
  version-pin: null
8
15
  sources:
9
16
  - url: https://docs.anthropic.com/en/docs/claude-code/memory
10
17
  anchor: '#claude-md-files'
18
+ hash: sha256:b6d5f2ae444b33ae686abf63de54471dfad7ff6d1bd57a9c5a6d69cb1096fae0
19
+ retrieved: 2026-06-07
11
20
  - url: https://docs.anthropic.com/en/docs/claude-code/settings
12
21
  anchor: '#configuration-precedence'
22
+ hash: sha256:664220cfa75c2236b9fc6f2ae7a278019eda3807858463121641a8d470f6e0b7
23
+ retrieved: 2026-06-07
13
24
  ---
14
25
 
15
26
  # CLAUDE.md Patterns
@@ -1,15 +1,25 @@
1
1
  ---
2
2
  name: coding-conventions
3
3
  description: Universal coding standards patterns across languages and linter/formatter configuration
4
- topics: [coding-standards, linting, formatting, naming, error-handling, code-style]
4
+ topics:
5
+ - coding-standards
6
+ - linting
7
+ - formatting
8
+ - naming
9
+ - error-handling
10
+ - code-style
5
11
  volatility: stable
6
- last-reviewed: null
12
+ last-reviewed: 2026-06-07
7
13
  version-pin: null
8
14
  sources:
9
15
  - url: https://google.github.io/styleguide/
10
16
  anchor: '#language-style-guides'
17
+ hash: sha256:250a15511160da60547e0daa20d398c1d0210ee4164a63001b0cc8272e3984ed
18
+ retrieved: 2026-06-07
11
19
  - url: https://peps.python.org/pep-0008/
12
20
  anchor: '#code-lay-out'
21
+ hash: sha256:8ed37af31c6b19c1384ef5c0cce501bd16d1a55d7984aed4a7d47c037ed5e7d5
22
+ retrieved: 2026-06-07
13
23
  ---
14
24
 
15
25
  # Coding Conventions
@@ -1,15 +1,26 @@
1
1
  ---
2
2
  name: database-design
3
3
  description: Database schema design, normalization, indexing, and migration patterns
4
- topics: [database, schema, sql, nosql, migrations, indexing, data-modeling]
4
+ topics:
5
+ - database
6
+ - schema
7
+ - sql
8
+ - nosql
9
+ - migrations
10
+ - indexing
11
+ - data-modeling
5
12
  volatility: stable
6
- last-reviewed: null
7
- version-pin: 'SQL:2023 / PostgreSQL 16'
13
+ last-reviewed: 2026-06-08
14
+ version-pin: SQL:2023 / PostgreSQL 16
8
15
  sources:
9
16
  - url: https://www.postgresql.org/docs/current/ddl.html
10
17
  anchor: '#data-definition'
18
+ hash: sha256:3cc4df5480a606056d90bd09b70beb02a09cfcf8942f7f7f233a2f608f225c8a
19
+ retrieved: 2026-06-08
11
20
  - url: https://www.iso.org/standard/76583.html
12
21
  anchor: '#sql-2023'
22
+ hash: sha256:647759512a829daa6b6df5e2b89ddd1935f8f28b47ecd040175cfecd53967807
23
+ retrieved: 2026-06-08
13
24
  ---
14
25
 
15
26
  ## Summary
@@ -1,15 +1,29 @@
1
1
  ---
2
2
  name: design-system-tokens
3
- description: Design token definitions, base component visual specs, dark mode patterns, and pattern library for building consistent UIs
4
- topics: [design-system, tokens, colors, typography, spacing, components, dark-mode, pattern-library]
3
+ description: >-
4
+ Design token definitions, base component visual specs, dark mode patterns, and pattern library for building consistent
5
+ UIs
6
+ topics:
7
+ - design-system
8
+ - tokens
9
+ - colors
10
+ - typography
11
+ - spacing
12
+ - components
13
+ - dark-mode
14
+ - pattern-library
5
15
  volatility: evolving
6
- last-reviewed: null
7
- version-pin: 'W3C Design Tokens Community Group Draft'
16
+ last-reviewed: 2026-06-08
17
+ version-pin: W3C Design Tokens Community Group Draft
8
18
  sources:
9
19
  - url: https://www.w3.org/community/design-tokens/
10
20
  anchor: '#format-module'
21
+ hash: sha256:a93801d1790645cc06a056d8e7b56a82fc509fc34b983f61a9d0c7c855b40679
22
+ retrieved: 2026-06-08
11
23
  - url: https://tr.designtokens.org/format/
12
24
  anchor: '#design-token-format'
25
+ hash: sha256:dc549a478159addede4fa9983998c05d3f8ca4b737a19cec738b618ddc8c46e4
26
+ retrieved: 2026-06-08
13
27
  ---
14
28
 
15
29
  ## Summary
@@ -1,13 +1,24 @@
1
1
  ---
2
2
  name: domain-modeling
3
3
  description: Domain-driven design patterns for identifying and modeling project domains
4
- topics: [ddd, domain-modeling, entities, aggregates, bounded-contexts, domain-events, value-objects]
4
+ topics:
5
+ - ddd
6
+ - domain-modeling
7
+ - entities
8
+ - aggregates
9
+ - bounded-contexts
10
+ - domain-events
11
+ - value-objects
5
12
  volatility: stable
6
- last-reviewed: null
13
+ last-reviewed: 2026-06-08
7
14
  version-pin: null
8
15
  sources:
9
16
  - url: https://martinfowler.com/bliki/BoundedContext.html
17
+ hash: sha256:5f6bbdd9567aeb45cb81d536a9e01a7636f2792ba41fa0abeff5603b74d46184
18
+ retrieved: 2026-06-08
10
19
  - url: https://martinfowler.com/bliki/DDD_Aggregate.html
20
+ hash: sha256:d0b5b35deca4e224e7c4dc131b6d15b3ae471bfb63a00aa8d96a27253540b91a
21
+ retrieved: 2026-06-08
11
22
  ---
12
23
 
13
24
  ## Summary
@@ -1,13 +1,23 @@
1
1
  ---
2
2
  name: eval-craft
3
3
  description: Writing effective project evals that verify AI-generated code meets documented standards
4
- topics: [evals, verification, coverage, adherence, consistency, structure, code-quality, standards-compliance]
4
+ topics:
5
+ - evals
6
+ - verification
7
+ - coverage
8
+ - adherence
9
+ - consistency
10
+ - structure
11
+ - code-quality
12
+ - standards-compliance
5
13
  volatility: fast-moving
6
- last-reviewed: null
14
+ last-reviewed: 2026-06-08
7
15
  version-pin: null
8
16
  sources:
9
17
  - url: https://docs.anthropic.com/en/docs/test-and-evaluate/eval-tool
10
18
  anchor: '#evaluation-tool'
19
+ hash: sha256:422a4935ddde89b5ae96896a83b9a19043c6316ff77bb6c94067e194b818bae0
20
+ retrieved: 2026-06-08
11
21
  ---
12
22
 
13
23
  # Eval Craft
@@ -1,15 +1,28 @@
1
1
  ---
2
2
  name: git-workflow-patterns
3
- description: Git branching strategies, commit conventions, PR workflows, merge policies, and CI integration patterns for AI-agent-driven development
4
- topics: [git, branching, commits, pull-requests, ci-cd, merge-strategy, worktrees]
3
+ description: >-
4
+ Git branching strategies, commit conventions, PR workflows, merge policies, and CI integration patterns for
5
+ AI-agent-driven development
6
+ topics:
7
+ - git
8
+ - branching
9
+ - commits
10
+ - pull-requests
11
+ - ci-cd
12
+ - merge-strategy
13
+ - worktrees
5
14
  volatility: stable
6
- last-reviewed: null
15
+ last-reviewed: 2026-06-08
7
16
  version-pin: null
8
17
  sources:
9
18
  - url: https://git-scm.com/docs/git-worktree
10
19
  anchor: '#_description'
20
+ hash: sha256:ab586ee537518edb32bab0c05a161fb2e37eaae0a0af82b99bca3e579fbd1a4b
21
+ retrieved: 2026-06-08
11
22
  - url: https://www.conventionalcommits.org/en/v1.0.0/
12
23
  anchor: '#specification'
24
+ hash: sha256:1f02d0f99e4a830daafa4cc75d92e1fe4aef50984c6c398aabd50d7c1214091f
25
+ retrieved: 2026-06-08
13
26
  ---
14
27
 
15
28
  # Git Workflow Patterns
@@ -1,13 +1,27 @@
1
1
  ---
2
2
  name: multi-model-research-dispatch
3
- description: Patterns for dispatching research and adversarial challenge to external AI models (Codex, Gemini) with reconciliation rules and single-model fallback
4
- topics: [multi-model, research, competitive-analysis, red-team, codex, gemini, dispatch, reconciliation]
3
+ description: >-
4
+ Patterns for dispatching research and adversarial challenge to external AI models (Codex, Gemini) with reconciliation
5
+ rules and single-model fallback
6
+ topics:
7
+ - multi-model
8
+ - research
9
+ - competitive-analysis
10
+ - red-team
11
+ - codex
12
+ - gemini
13
+ - dispatch
14
+ - reconciliation
5
15
  volatility: fast-moving
6
- last-reviewed: null
16
+ last-reviewed: 2026-06-08
7
17
  version-pin: null
8
18
  sources:
9
19
  - url: https://ai.google.dev/gemini-api/docs
20
+ hash: sha256:a681af04a57814c2e8944026b48201b3aaee9d55bf9a457aeaac06fae4fe735c
21
+ retrieved: 2026-06-08
10
22
  - url: https://docs.anthropic.com/en/docs/claude-code/cli-reference
23
+ hash: sha256:5bb925357a3d47aa312938c71d8ea742cf89ef77ad3727142e603cf3f7d0f096
24
+ retrieved: 2026-06-08
11
25
  ---
12
26
 
13
27
  # Multi-Model Research Dispatch
@@ -1,13 +1,25 @@
1
1
  ---
2
2
  name: multi-model-review-dispatch
3
- description: Patterns for dispatching reviews to AI CLI tools (Codex, Gemini, Claude), including fallback strategies and finding reconciliation
4
- topics: [multi-model, code-review, codex, gemini, claude, review-synthesis]
3
+ description: >-
4
+ Patterns for dispatching reviews to AI CLI tools (Codex, Gemini, Claude), including fallback strategies and finding
5
+ reconciliation
6
+ topics:
7
+ - multi-model
8
+ - code-review
9
+ - codex
10
+ - gemini
11
+ - claude
12
+ - review-synthesis
5
13
  volatility: fast-moving
6
- last-reviewed: null
14
+ last-reviewed: 2026-06-08
7
15
  version-pin: null
8
16
  sources:
9
17
  - url: https://ai.google.dev/gemini-api/docs
18
+ hash: sha256:7039ac6e2ce9e12c83e0a6d2d48b94dde4fd498ee213582ea4fee57c30bf11bf
19
+ retrieved: 2026-06-08
10
20
  - url: https://docs.anthropic.com/en/docs/claude-code/cli-reference
21
+ hash: sha256:5bb925357a3d47aa312938c71d8ea742cf89ef77ad3727142e603cf3f7d0f096
22
+ retrieved: 2026-06-08
11
23
  ---
12
24
 
13
25
  # Multi-Model Review Dispatch
@@ -1,12 +1,19 @@
1
1
  ---
2
2
  name: multi-service-api-contracts
3
3
  description: Internal API versioning, backward compatibility, retries, and idempotency patterns
4
- topics: [internal-api-versioning, backward-compatibility, retries, idempotency, contract-evolution]
4
+ topics:
5
+ - internal-api-versioning
6
+ - backward-compatibility
7
+ - retries
8
+ - idempotency
9
+ - contract-evolution
5
10
  volatility: evolving
6
- last-reviewed: null
7
- version-pin: 'RFC 9110'
11
+ last-reviewed: 2026-06-08
12
+ version-pin: RFC 9110
8
13
  sources:
9
14
  - url: https://www.rfc-editor.org/rfc/rfc9110
15
+ hash: sha256:0caffc54edcc671a0655b58136d0675d844e2d78ae7810c5b85464b930335ab8
16
+ retrieved: 2026-06-08
10
17
  ---
11
18
 
12
19
  ## Summary
@@ -1,12 +1,20 @@
1
1
  ---
2
2
  name: multi-service-architecture
3
3
  description: Service boundary design, communication patterns, service discovery, and networking topology
4
- topics: [service-boundaries, communication-patterns, service-discovery, networking-topology, data-ownership, sync-vs-async]
4
+ topics:
5
+ - service-boundaries
6
+ - communication-patterns
7
+ - service-discovery
8
+ - networking-topology
9
+ - data-ownership
10
+ - sync-vs-async
5
11
  volatility: evolving
6
- last-reviewed: null
12
+ last-reviewed: 2026-06-08
7
13
  version-pin: null
8
14
  sources:
9
15
  - url: https://docs.aws.amazon.com/whitepapers/latest/microservices-on-aws/microservices-on-aws.html
16
+ hash: sha256:4d499bab739ac9e54cda4a1678f1f9157d4edb75b3eaff33f31b3eef6b1a8112
17
+ retrieved: 2026-06-08
10
18
  ---
11
19
 
12
20
  ## Summary
@@ -1,13 +1,22 @@
1
1
  ---
2
2
  name: multi-service-auth
3
3
  description: Mutual TLS, service tokens, zero-trust architecture, and audience scoping
4
- topics: [mtls, service-tokens, zero-trust, audience-scoping, token-rotation]
4
+ topics:
5
+ - mtls
6
+ - service-tokens
7
+ - zero-trust
8
+ - audience-scoping
9
+ - token-rotation
5
10
  volatility: evolving
6
- last-reviewed: null
7
- version-pin: 'RFC 6749 / OIDC Core 1.0'
11
+ last-reviewed: 2026-06-08
12
+ version-pin: RFC 6749 / OIDC Core 1.0
8
13
  sources:
9
14
  - url: https://www.rfc-editor.org/rfc/rfc6749
15
+ hash: sha256:bafc555f829aaf66ff2ac7f0d8a7c1fdda1f8b41fb876e34f3b340a542789ab8
16
+ retrieved: 2026-06-08
10
17
  - url: https://openid.net/specs/openid-connect-core-1_0.html
18
+ hash: sha256:4d016752a645e8a3c259baa4173b5a90cb6c82898ce868fc8444adde262a5aed
19
+ retrieved: 2026-06-08
11
20
  ---
12
21
 
13
22
  ## Summary
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zigrivers/scaffold",
3
- "version": "3.33.5",
3
+ "version": "3.33.7",
4
4
  "description": "AI-powered software project scaffolding pipeline",
5
5
  "type": "module",
6
6
  "workspaces": [