@geraldmaron/construct 1.0.5 → 1.0.6

package/rules/common/security.md

@@ -1,5 +1,5 @@
 <!--
-rules/common/security.md — mandatory security checks and secret management.
+rules/common/security.md: mandatory security checks and secret management.
 
 Defines pre-commit security checklist, secret management rules,
 and response protocol for discovered vulnerabilities.

package/rules/common/skill-composition.md

@@ -1,5 +1,5 @@
 <!--
-rules/common/skill-composition.md — how specialist prompts compose with skill files.
+rules/common/skill-composition.md: how specialist prompts compose with skill files.
 
 Defines the default boundary between what lives in the agent's base prompt and
 what is fetched via `get_skill` at runtime. Aims to keep prompts lean while
@@ -17,13 +17,13 @@ Every specialist prompt carries a marker:
 **Role guidance**: call `get_skill("roles/NAME")` before drafting.
 ```
 
-When the agent begins substantive work in its domain, it calls `get_skill("roles/NAME")` via the construct-mcp server. The skill body is returned for that turn only — no permanent prompt budget is consumed.
+When the agent begins substantive work in its domain, it calls `get_skill("roles/NAME")` via the construct-mcp server. The skill body is returned for that turn only: no permanent prompt budget is consumed.
 
 All hosts Construct supports (Claude Code, OpenCode, Codex, Copilot) have `get_skill` available through the construct-mcp server, so the runtime call is reliable.
 
 ## Why on-demand is the default
 
-Inlining every role skill at sync time used to consume ~1000–2000 words of prompt budget per specialist, regardless of whether the skill content was relevant to the current task. That budget is fixed — it reduces the window available for actual context.
+Inlining every role skill at sync time used to consume ~1000–2000 words of prompt budget per specialist, regardless of whether the skill content was relevant to the current task. That budget is fixed: it reduces the window available for actual context.
 
 On-demand loading means:
 
@@ -40,20 +40,20 @@ Set `preloadRoleGuidance: true` on a registry entry only when:
 - The role content is so load-bearing that every single turn needs it
 - The agent's model is weak at tool-calling discipline and skips the `get_skill` call in practice
 
-This should be rare. If you find yourself preloading most agents, revisit the reasoning — the default exists because the cost is real.
+This should be rare. If you find yourself preloading most agents, revisit the reasoning: the default exists because the cost is real.
 
 ## Skill array vs. role guidance
 
 Two different mechanisms for two different purposes:
 
-- **Registry `skills: [...]` array** — declarative metadata listing which skills the agent is *entitled* to call. Not inlined into the prompt. Used by `list_skills`, routing heuristics, and audit tooling. Add skills here liberally.
-- **Role guidance directive** — the single `**Role guidance**: call get_skill("roles/NAME")` line in the prompt. Points the agent at its role file and (by default) tells it to load on demand. Exactly one per agent.
+- **Registry `skills: [...]` array**: declarative metadata listing which skills the agent is *entitled* to call. Not inlined into the prompt. Used by `list_skills`, routing heuristics, and audit tooling. Add skills here liberally.
+- **Role guidance directive**: the single `**Role guidance**: call get_skill("roles/NAME")` line in the prompt. Points the agent at its role file and (by default) tells it to load on demand. Exactly one per agent.
 
 ## Contributor guidance
 
 When adding or editing a specialist:
 
-1. Keep the base prompt short — role, perspective, productive tension, handoff contract. Under 400 words is normal.
+1. Keep the base prompt short: role, perspective, productive tension, handoff contract. Under 400 words is normal.
 2. Put domain depth into `skills/roles/NAME.md` and optional flavor overlays like `skills/roles/NAME.FLAVOR.md`.
 3. Leave the role-guidance directive in place. Do not manually inline role content into the prompt body.
 4. Only add `preloadRoleGuidance: true` with a written reason in the registry description.
@@ -64,4 +64,4 @@ Do not:
 
 - Paste role-skill content directly into the prompt body "to be safe"
 - Add `preloadRoleGuidance: true` to push a prompt under the cap without fixing the underlying bloat
-- Split a role skill into many tiny files to dodge the cap — keep the cohesive unit, load it on demand instead
+- Split a role skill into many tiny files to dodge the cap: keep the cohesive unit, load it on demand instead

package/rules/common/testing.md

@@ -1,5 +1,5 @@
 <!--
-rules/common/testing.md — test coverage requirements and TDD workflow.
+rules/common/testing.md: test coverage requirements and TDD workflow.
 
 Defines minimum 80% coverage, TDD red-green-refactor cycle,
 AAA test structure, and descriptive naming conventions.

package/rules/golang/coding-style.md

@@ -1,5 +1,5 @@
 <!--
-rules/golang/coding-style.md — <one-line purpose>
+rules/golang/coding-style.md: <one-line purpose>
 
 <2–6 line summary.>
 -->
@@ -15,7 +15,7 @@ paths:
 
 ## Formatting
 
-- **gofmt** and **goimports** are mandatory — no style debates
+- **gofmt** and **goimports** are mandatory: no style debates
 
 ## Design Principles
 

package/rules/golang/hooks.md

@@ -1,5 +1,5 @@
 <!--
-rules/golang/hooks.md — <one-line purpose>
+rules/golang/hooks.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/golang/patterns.md

@@ -1,5 +1,5 @@
 <!--
-rules/golang/patterns.md — <one-line purpose>
+rules/golang/patterns.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/golang/security.md

@@ -1,5 +1,5 @@
 <!--
-rules/golang/security.md — <one-line purpose>
+rules/golang/security.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/golang/testing.md

@@ -1,5 +1,5 @@
 <!--
-rules/golang/testing.md — <one-line purpose>
+rules/golang/testing.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/python/coding-style.md

@@ -1,5 +1,5 @@
 <!--
-rules/python/coding-style.md — <one-line purpose>
+rules/python/coding-style.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/python/hooks.md

@@ -1,5 +1,5 @@
 <!--
-rules/python/hooks.md — <one-line purpose>
+rules/python/hooks.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/python/patterns.md

@@ -1,5 +1,5 @@
 <!--
-rules/python/patterns.md — <one-line purpose>
+rules/python/patterns.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/python/security.md

@@ -1,5 +1,5 @@
 <!--
-rules/python/security.md — <one-line purpose>
+rules/python/security.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/python/testing.md

@@ -1,5 +1,5 @@
 <!--
-rules/python/testing.md — <one-line purpose>
+rules/python/testing.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/swift/coding-style.md

@@ -1,5 +1,5 @@
 <!--
-rules/swift/coding-style.md — <one-line purpose>
+rules/swift/coding-style.md: <one-line purpose>
 
 <2–6 line summary.>
 -->
@@ -19,14 +19,14 @@ paths:
 
 ## Immutability
 
-- Prefer `let` over `var` — define everything as `let` and only change to `var` if the compiler requires it
+- Prefer `let` over `var`: define everything as `let` and only change to `var` if the compiler requires it
 - Use `struct` with value semantics by default; use `class` only when identity or reference semantics are needed
 
 ## Naming
 
 Follow [Apple API Design Guidelines](https://www.swift.org/documentation/api-design-guidelines/):
 
-- Clarity at the point of use — omit needless words
+- Clarity at the point of use: omit needless words
 - Name methods and properties for their roles, not their types
 - Use `static let` for constants over global constants
 

package/rules/swift/hooks.md

@@ -1,5 +1,5 @@
 <!--
-rules/swift/hooks.md — <one-line purpose>
+rules/swift/hooks.md: <one-line purpose>
 
 <2–6 line summary.>
 -->
@@ -18,4 +18,4 @@ paths:
 
 ## Warning
 
-Flag `print()` statements — use `os.Logger` or structured logging instead for production code.
+Flag `print()` statements: use `os.Logger` or structured logging instead for production code.

package/rules/swift/patterns.md

@@ -1,5 +1,5 @@
 <!--
-rules/swift/patterns.md — <one-line purpose>
+rules/swift/patterns.md: <one-line purpose>
 
 <2–6 line summary.>
 -->
@@ -53,7 +53,7 @@ actor Cache<Key: Hashable & Sendable, Value: Sendable> {
 
 ## Dependency Injection
 
-Inject protocols with default parameters — production uses defaults, tests inject mocks:
+Inject protocols with default parameters: production uses defaults, tests inject mocks:
 
 ```swift
 struct UserService {

package/rules/swift/security.md

@@ -1,5 +1,5 @@
 <!--
-rules/swift/security.md — <one-line purpose>
+rules/swift/security.md: <one-line purpose>
 
 <2–6 line summary.>
 -->
@@ -14,9 +14,9 @@ paths:
 
 ## Secret Management
 
-- Use **Keychain Services** for sensitive data (tokens, passwords, keys) — never `UserDefaults`
+- Use **Keychain Services** for sensitive data (tokens, passwords, keys): never `UserDefaults`
 - Use environment variables or `.xcconfig` files for build-time secrets
-- Never hardcode secrets in source — decompilation tools extract them trivially
+- Never hardcode secrets in source: decompilation tools extract them trivially
 
 ```swift
 let apiKey = ProcessInfo.processInfo.environment["API_KEY"]
@@ -27,7 +27,7 @@ guard let apiKey, !apiKey.isEmpty else {
 
 ## Transport Security
 
-- App Transport Security (ATS) is enforced by default — do not disable it
+- App Transport Security (ATS) is enforced by default: do not disable it
 - Use certificate pinning for critical endpoints
 - Validate all server certificates
 

package/rules/swift/testing.md

@@ -1,5 +1,5 @@
 <!--
-rules/swift/testing.md — <one-line purpose>
+rules/swift/testing.md: <one-line purpose>
 
 <2–6 line summary.>
 -->
@@ -27,7 +27,7 @@ func userCreationValidatesEmail() throws {
 
 ## Test Isolation
 
-Each test gets a fresh instance — set up in `init`, tear down in `deinit`. No shared mutable state between tests.
+Each test gets a fresh instance: set up in `init`, tear down in `deinit`. No shared mutable state between tests.
 
 ## Parameterized Tests
 

package/rules/typescript/coding-style.md

@@ -1,5 +1,5 @@
 <!--
-rules/typescript/coding-style.md — <one-line purpose>
+rules/typescript/coding-style.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/typescript/hooks.md

@@ -1,5 +1,5 @@
 <!--
-rules/typescript/hooks.md — <one-line purpose>
+rules/typescript/hooks.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/typescript/patterns.md

@@ -1,5 +1,5 @@
 <!--
-rules/typescript/patterns.md — <one-line purpose>
+rules/typescript/patterns.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/typescript/security.md

@@ -1,5 +1,5 @@
 <!--
-rules/typescript/security.md — <one-line purpose>
+rules/typescript/security.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/typescript/testing.md

@@ -1,5 +1,5 @@
 <!--
-rules/typescript/testing.md — <one-line purpose>
+rules/typescript/testing.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/web/coding-style.md

@@ -1,5 +1,5 @@
 <!--
-rules/web/coding-style.md — <one-line purpose>
+rules/web/coding-style.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/web/design-quality.md

@@ -1,5 +1,5 @@
 <!--
-rules/web/design-quality.md — <one-line purpose>
+rules/web/design-quality.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/web/hooks.md

@@ -1,5 +1,5 @@
 <!--
-rules/web/hooks.md — <one-line purpose>
+rules/web/hooks.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/web/patterns.md

@@ -1,5 +1,5 @@
 <!--
-rules/web/patterns.md — <one-line purpose>
+rules/web/patterns.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/web/performance.md

@@ -1,5 +1,5 @@
 <!--
-rules/web/performance.md — <one-line purpose>
+rules/web/performance.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/web/security.md

@@ -1,5 +1,5 @@
 <!--
-rules/web/security.md — <one-line purpose>
+rules/web/security.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/rules/web/testing.md

@@ -1,5 +1,5 @@
 <!--
-rules/web/testing.md — <one-line purpose>
+rules/web/testing.md: <one-line purpose>
 
 <2–6 line summary.>
 -->

package/skills/ai/agent-dev.md

@@ -1,5 +1,5 @@
 <!--
-skills/ai/agent-dev.md — AI Agent Development — Use this skill when building AI agents, tool-use systems, or multi-agent workflo
+skills/ai/agent-dev.md (AI Agent Development) Use this skill when building AI agents, tool-use systems, or multi-agent workflo
 
 Use this skill when building AI agents, tool-use systems, or multi-agent workflows. ## Agent Architecture
 -->

package/skills/ai/llm-security.md

@@ -1,5 +1,5 @@
 <!--
-skills/ai/llm-security.md — LLM Security — Use this skill when securing LLM-powered applications against prompt injection,
+skills/ai/llm-security.md (LLM Security) Use this skill when securing LLM-powered applications against prompt injection,
 
 Use this skill when securing LLM-powered applications against prompt injection, data leakage, and misuse. ## Prompt Injection
 -->

package/skills/ai/ml-ops.md

@@ -1,5 +1,5 @@
 <!--
-skills/ai/ml-ops.md — ML Operations (MLOps) — ```
+skills/ai/ml-ops.md (ML Operations (MLOps)) ```
 
 ## The MLOps Lifecycle ```
 -->
@@ -86,7 +86,7 @@ Central store for model versions and deployment state:
 
 | Stage | Meaning |
 |---|---|
-| Staging | Candidate — passes evaluation, not yet in production |
+| Staging | Candidate: passes evaluation, not yet in production |
 | Production | Currently serving |
 | Archived | Superseded |
 
@@ -117,7 +117,7 @@ async def predict(req: PredictRequest) -> PredictResponse:
 
 ### A/B testing / Shadow mode
 
-- **Shadow mode**: new model receives traffic and logs predictions but does not serve users — validate before switching
+- **Shadow mode**: new model receives traffic and logs predictions but does not serve users: validate before switching
 - **A/B test**: split traffic (e.g., 10% new model) and measure business metrics, not just accuracy
 - Use a feature flag system to control routing
 
@@ -162,8 +162,8 @@ Trigger retraining when:
 
 ## Common Pitfalls
 
-- **Training-serving skew**: feature engineering in training differs from serving — solve with a shared feature pipeline
-- **Data leakage**: future information in training features inflates metrics — use strict temporal splits
+- **Training-serving skew**: feature engineering in training differs from serving: solve with a shared feature pipeline
+- **Data leakage**: future information in training features inflates metrics: use strict temporal splits
 - **Model staleness without detection**: set up drift monitoring day 1, not after the model degrades
 - **No rollback plan**: always keep N-1 model version in registry and test rollback procedure
-- **GPU waste**: jobs that could run on CPU scheduled on GPU — profile resource usage
+- **GPU waste**: jobs that could run on CPU scheduled on GPU: profile resource usage

package/skills/ai/orchestration-workflow.md

@@ -1,5 +1,5 @@
 <!--
-skills/ai/orchestration-workflow.md — Construct Orchestration Workflow — Use this skill when the request involves agent orchestration, phase transitions,
+skills/ai/orchestration-workflow.md (Construct Orchestration Workflow) Use this skill when the request involves agent orchestration, phase transitions,
 
 Use this skill when the request involves agent orchestration, phase transitions, task keys, handoff quality, workflow state, or project alignment. ## Core Model
 -->

package/skills/ai/prompt-and-eval.md

@@ -1,5 +1,5 @@
 <!--
-skills/ai/prompt-and-eval.md — Prompt Engineering and Evaluation — Use this skill when designing prompts, evaluating model performance, or optimizi
+skills/ai/prompt-and-eval.md (Prompt Engineering and Evaluation) Use this skill when designing prompts, evaluating model performance, or optimizi
 
 Use this skill when designing prompts, evaluating model performance, or optimizing LLM behavior. ## Prompt Structure
 -->

package/skills/ai/prompt-optimizer.md

@@ -1,5 +1,5 @@
 <!--
-skills/ai/prompt-optimizer.md — Closed-loop prompt auto-optimization guide.
+skills/ai/prompt-optimizer.md: Closed-loop prompt auto-optimization guide.
 
 Uses telemetry traces and quality scores as the feedback signal, Claude as the optimizer,
 and the agent registry + construct sync as the deployment layer.
@@ -24,15 +24,15 @@ construct optimize --list
 construct optimize cx-debugger --threshold=0.65 --days=14 --min-traces=15
 ```
 
-The optimizer requires Python 3.12+ (`pip3` must be available). It will auto-install `dspy-ai` and `requests` on first run. Set `ANTHROPIC_API_KEY` or `OPENAI_API_KEY` in `.env`. DSPy uses the same LLM key Construct uses — no separate setup.
+The optimizer requires Python 3.12+ (`pip3` must be available). It will auto-install `dspy-ai` and `requests` on first run. Set `ANTHROPIC_API_KEY` or `OPENAI_API_KEY` in `.env`. DSPy uses the same LLM key Construct uses: no separate setup.
 
 ## When to run
 
 - Triggered by `/work:optimize-prompts` (manual) or the scheduled task `prompt-optimization-weekly`
 - Automatically suggested when `cx-trace-reviewer` finds an agent with median quality score below 0.65 over the past 7 days
-- Never run optimization on prompts with fewer than 20 scored traces — insufficient signal
+- Never run optimization on prompts with fewer than 20 scored traces: insufficient signal
 
-## Step 1 — Gather signal
+## Step 1: Gather signal
 
 Retrieve the current production prompt for the target agent from `agents/registry.json` (or the corresponding `promptFile` if using extracted prompts).
 
@@ -50,7 +50,7 @@ GET {CONSTRUCT_TELEMETRY_URL}/api/public/scores?traceId={id}&name=quality
 
 Filter to scores where `value < 0.7`. For each low-scoring trace, extract: the prompt used, the user input, the model output, the quality score, and any human comments.
 
-## Step 2 — Diagnose failure patterns
+## Step 2: Diagnose failure patterns
 
 Analyze the low-scoring traces as a batch. Identify recurring failure modes. Common patterns:
 
@@ -65,16 +65,16 @@ Analyze the low-scoring traces as a batch. Identify recurring failure modes. Com
 
 Write a failure summary: top 3 patterns with supporting trace count and representative examples.
 
-## Step 3 — Generate improved prompt
+## Step 3: Generate improved prompt
 
 Write an improved prompt that directly addresses the diagnosed failures. Rules:
 
-1. **Keep what works** — compare high-scoring traces (>0.8) to low-scoring ones. Only change what's associated with failures.
-2. **Surgical edits, not rewrites** — changing everything risks breaking current strengths. Identify the specific clauses that correlate with failures.
-3. **Be explicit, not vague** — if the failure is "too verbose", add a concrete rule ("respond in under 150 words for questions that fit on one line") not a general note ("be concise").
-4. **Add a self-check instruction** — append a brief checklist the agent runs before responding, derived from the top failure patterns.
+1. **Keep what works**: compare high-scoring traces (>0.8) to low-scoring ones. Only change what's associated with failures.
+2. **Surgical edits, not rewrites**: changing everything risks breaking current strengths. Identify the specific clauses that correlate with failures.
+3. **Be explicit, not vague**: if the failure is "too verbose", add a concrete rule ("respond in under 150 words for questions that fit on one line") not a general note ("be concise").
+4. **Add a self-check instruction**: append a brief checklist the agent runs before responding, derived from the top failure patterns.
 
-## Step 4 — Push to staging
+## Step 4: Push to staging
 
 Update the agent's prompt in `agents/registry.json` (or the corresponding `promptFile`) with a staging marker comment. Tag the version by writing to `.cx/decisions/prompt-staging-{agent}-{date}.md`.
 
@@ -82,7 +82,7 @@ Log the candidate prompt as a span attribute on a test run batch using `cx_trace
 
 Do not overwrite the production prompt in the registry until promotion is confirmed.
 
-## Step 5 — Monitor staging
+## Step 5: Monitor staging
 
 After at least 20 scored traces on the staging version:
 - Compare median quality score: staging vs production
@@ -91,7 +91,7 @@ After at least 20 scored traces on the staging version:
 
 To promote: update the agent registry with the accepted prompt and run `construct sync`.
 
-## Step 6 — Document the optimization
+## Step 6: Document the optimization
 
 Write to `.cx/decisions/` with:
 - Which agent was optimized

package/skills/ai/rag-system.md

@@ -1,5 +1,5 @@
 <!--
-skills/ai/rag-system.md — RAG System Design — Use this skill when building retrieval-augmented generation pipelines, vector se
+skills/ai/rag-system.md (RAG System Design) Use this skill when building retrieval-augmented generation pipelines, vector se
 
 Use this skill when building retrieval-augmented generation pipelines, vector search, or knowledge-grounded AI systems. ## Document Processing
 -->

package/skills/architecture/api-design.md

@@ -1,5 +1,5 @@
 <!--
-skills/architecture/api-design.md — API Design — Use this skill when designing REST, GraphQL, or gRPC APIs.
+skills/architecture/api-design.md (API Design) Use this skill when designing REST, GraphQL, or gRPC APIs.
 
 Use this skill when designing REST, GraphQL, or gRPC APIs. ## REST Design Principles
 -->

package/skills/architecture/caching.md

@@ -1,5 +1,5 @@
 <!--
-skills/architecture/caching.md — Caching — Use this skill when designing caching strategies for applications, APIs, or infr
+skills/architecture/caching.md (Caching) Use this skill when designing caching strategies for applications, APIs, or infr
 
 Use this skill when designing caching strategies for applications, APIs, or infrastructure. ## Cache Layers
 -->

package/skills/architecture/cloud-native.md

@@ -1,5 +1,5 @@
 <!--
-skills/architecture/cloud-native.md — Cloud-Native Architecture — Use this skill when designing containerized, orchestrated, or microservice-based
+skills/architecture/cloud-native.md (Cloud-Native Architecture) Use this skill when designing containerized, orchestrated, or microservice-based
 
 Use this skill when designing containerized, orchestrated, or microservice-based systems. ## Container Best Practices
 -->

package/skills/architecture/message-queue.md

@@ -1,5 +1,5 @@
 <!--
-skills/architecture/message-queue.md — Message Queues and Event-Driven Architecture — Use this skill when designing asynchronous communication, event-driven systems,
+skills/architecture/message-queue.md (Message Queues and Event-Driven Architecture) Use this skill when designing asynchronous communication, event-driven systems,
 
 Use this skill when designing asynchronous communication, event-driven systems, or message-based integrations. ## When to Use Message Queues
 -->

package/skills/architecture/security-arch.md

@@ -1,5 +1,5 @@
 <!--
-skills/architecture/security-arch.md — Security Architecture — Use this skill when designing authentication, authorization, network security, o
+skills/architecture/security-arch.md (Security Architecture) Use this skill when designing authentication, authorization, network security, o
 
 Use this skill when designing authentication, authorization, network security, or zero-trust architectures. ## Zero Trust Principles
 -->

package/skills/compliance/ai-disclosure.md

@@ -1,5 +1,5 @@
 <!--
-skills/compliance/ai-disclosure.md — AI Disclosure — AI transparency, disclosure, and regulatory compliance.
+skills/compliance/ai-disclosure.md (AI Disclosure) AI transparency, disclosure, and regulatory compliance.
 
 Use this skill when reviewing AI features for disclosure requirements, transparency obligations, or emerging AI regulation compliance.
 -->

package/skills/compliance/data-privacy.md

@@ -1,5 +1,5 @@
 <!--
-skills/compliance/data-privacy.md — Data Privacy — GDPR, CCPA, and data protection compliance patterns.
+skills/compliance/data-privacy.md (Data Privacy) GDPR, CCPA, and data protection compliance patterns.
 
 Use this skill when reviewing data collection, storage, processing, or retention for privacy regulation compliance.
 -->

package/skills/compliance/license-audit.md

@@ -1,5 +1,5 @@
 <!--
-skills/compliance/license-audit.md — License Audit — Dependency license review and open-source compliance.
+skills/compliance/license-audit.md (License Audit) Dependency license review and open-source compliance.
 
 Use this skill when auditing dependency licenses, evaluating OSS compliance risk, or preparing license inventories for legal review.
 -->
@@ -24,7 +24,7 @@ Use this skill when auditing dependency licenses, evaluating OSS compliance risk
 3. Map each dependency to its SPDX license identifier
 4. Flag any dependency without a clear license file as unknown-risk
 5. Check for license changes between pinned versions and latest
-6. Look past layer one — transitive copyleft taints the whole tree
+6. Look past layer one: transitive copyleft taints the whole tree
 
 ## Red Flags
 

package/skills/compliance/regulatory-review.md

@@ -1,5 +1,5 @@
 <!--
-skills/compliance/regulatory-review.md — Regulatory Review — Pre-ship compliance review checklist and process.
+skills/compliance/regulatory-review.md (Regulatory Review) Pre-ship compliance review checklist and process.
 
 Use this skill when conducting a compliance review before shipping features that handle user data, financial transactions, AI decisions, or regulated content.
 -->

package/skills/development/cpp.md

@@ -1,5 +1,5 @@
 <!--
-skills/development/cpp.md — C/C++ Best Practices — Use this skill when writing, reviewing, or debugging C or C++ code.
+skills/development/cpp.md (C/C++ Best Practices) Use this skill when writing, reviewing, or debugging C or C++ code.
 
 Use this skill when writing, reviewing, or debugging C or C++ code. ## Project Structure
 -->

package/skills/development/go.md

@@ -1,5 +1,5 @@
 <!--
-skills/development/go.md — Go Best Practices — Use this skill when writing, reviewing, or debugging Go code.
+skills/development/go.md (Go Best Practices) Use this skill when writing, reviewing, or debugging Go code.
 
 Use this skill when writing, reviewing, or debugging Go code. ## Project Structure
 -->

package/skills/development/java.md

@@ -1,5 +1,5 @@
 <!--
-skills/development/java.md — Java Best Practices — Use this skill when writing, reviewing, or debugging Java or Kotlin code on the
+skills/development/java.md (Java Best Practices) Use this skill when writing, reviewing, or debugging Java or Kotlin code on the
 
 Use this skill when writing, reviewing, or debugging Java or Kotlin code on the JVM. ## Project Structure
 -->