@geraldmaron/construct 1.0.14 → 1.0.15

package/rules/common/patterns.md

@@ -1,8 +1,6 @@
-<!--
-rules/common/patterns.md: reusable design patterns and skeleton project strategy.
-
-Covers skeleton project evaluation, repository pattern, and API response format.
--->
+---
+description: reusable design patterns and skeleton project strategy.
+---
 # Common Patterns
 
 ## Skeleton Projects

package/rules/common/release-gates.md

@@ -1,11 +1,6 @@
-<!--
-rules/common/release-gates.md: Hard release gates for Construct work.
-
-Defines the blocking contracts every agent and persona must satisfy locally
-before any commit, push, or "done" claim. Loaded by the construct persona,
-AGENTS.md, and the engineer/reviewer/operator role overlays. Enforcement is at
-the prompt level: CI is a backstop, not the primary gate.
--->
+---
+description: Hard release gates for Construct work.
+---
 # Release Gates: Hard Contracts
 
 These are blocking gates. Every agent, persona, and harness session working in or shipping Construct must satisfy them locally **before** any commit, push, or "done" claim. CI is a backstop, not the primary check.

package/rules/common/research.md

@@ -1,11 +1,6 @@
-<!--
-rules/common/research.md: canonical research and evidence policy for Construct.
-
-Defines how research starts, which sources to prefer, how claims are verified,
-and what must be recorded so findings are reproducible. Applies to research,
-product evidence synthesis, document ingest follow-up, and any recommendation
-that depends on external facts or evolving internal evidence.
--->
+---
+description: canonical research and evidence policy for Construct.
+---
 # Research Policy
 
 Construct treats research as a reproducible evidence-gathering process, not free-form browsing. If a claim could change decisions, scope, architecture, or roadmap, it must be tied to verifiable evidence.

package/rules/common/review-before-change.md

@@ -1,11 +1,6 @@
-<!--
-rules/common/review-before-change.md: audit the current state before authoring anything new.
-
-Applies to every specialist on every platform. Pairs with framing.md (frame the
-problem) and development-workflow.md step 0 (research and reuse before code).
-This rule extends the same discipline to artifacts: docs, strategy, PRDs, ADRs,
-RFCs, rules, templates, and any other durable file. Read before scaffolding.
--->
+---
+description: audit the current state before authoring anything new.
+---
 # Review Before Change
 
 Before creating or rewriting a durable artifact, check what already exists.
@@ -54,5 +49,4 @@ For artifacts that go through a review cycle (strategy, PRD, ADR, RFC), the fram
 ## Related
 
 - `rules/common/framing.md`: frame the underlying problem before reaching for inputs.
-- `rules/common/development-workflow.md`: step 0 covers the same discipline for code.
 - `rules/common/doc-ownership.md`: which specialist owns which artifact type.

package/rules/common/security.md

@@ -1,9 +1,6 @@
-<!--
-rules/common/security.md: mandatory security checks and secret management.
-
-Defines pre-commit security checklist, secret management rules,
-and response protocol for discovered vulnerabilities.
--->
+---
+description: mandatory security checks and secret management.
+---
 # Security Guidelines
 
 ## Mandatory Security Checks

package/rules/common/skill-composition.md

@@ -1,10 +1,6 @@
-<!--
-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
-keeping domain knowledge reliably available when needed.
--->
+---
+description: how specialist prompts compose with skill files.
+---
 # Skill Composition Policy
 
 Specialist agent prompts are lean on purpose. Domain depth lives in skill files and is pulled in on demand, not pre-inlined.

package/rules/common/testing.md

@@ -1,9 +1,6 @@
-<!--
-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.
--->
+---
+description: test coverage requirements and TDD workflow.
+---
 # Testing Requirements
 
 ## Minimum Test Coverage: 80%

package/rules/golang/coding-style.md

@@ -1,9 +1,5 @@
-<!--
-rules/golang/coding-style.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct golang coding style rule. Applies to files matching **/*.go, **/go.mod, **/go.sum. Use when writing or reviewing golang code that involves coding style.
 paths:
   - "**/*.go"
   - "**/go.mod"

package/rules/golang/hooks.md

@@ -1,9 +1,5 @@
-<!--
-rules/golang/hooks.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct golang hooks rule. Applies to files matching **/*.go, **/go.mod, **/go.sum. Use when writing or reviewing golang code that involves hooks.
 paths:
   - "**/*.go"
   - "**/go.mod"

package/rules/golang/patterns.md

@@ -1,9 +1,5 @@
-<!--
-rules/golang/patterns.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct golang patterns rule. Applies to files matching **/*.go, **/go.mod, **/go.sum. Use when writing or reviewing golang code that involves patterns.
 paths:
   - "**/*.go"
   - "**/go.mod"

package/rules/golang/security.md

@@ -1,9 +1,5 @@
-<!--
-rules/golang/security.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct golang security rule. Applies to files matching **/*.go, **/go.mod, **/go.sum. Use when writing or reviewing golang code that involves security.
 paths:
   - "**/*.go"
   - "**/go.mod"

package/rules/golang/testing.md

@@ -1,9 +1,5 @@
-<!--
-rules/golang/testing.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct golang testing rule. Applies to files matching **/*.go, **/go.mod, **/go.sum. Use when writing or reviewing golang code that involves testing.
 paths:
   - "**/*.go"
   - "**/go.mod"

package/rules/python/coding-style.md

@@ -1,9 +1,5 @@
-<!--
-rules/python/coding-style.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct python coding style rule. Applies to files matching **/*.py, **/*.pyi. Use when writing or reviewing python code that involves coding style.
 paths:
   - "**/*.py"
   - "**/*.pyi"

package/rules/python/hooks.md

@@ -1,9 +1,5 @@
-<!--
-rules/python/hooks.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct python hooks rule. Applies to files matching **/*.py, **/*.pyi. Use when writing or reviewing python code that involves hooks.
 paths:
   - "**/*.py"
   - "**/*.pyi"

package/rules/python/patterns.md

@@ -1,9 +1,5 @@
-<!--
-rules/python/patterns.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct python patterns rule. Applies to files matching **/*.py, **/*.pyi. Use when writing or reviewing python code that involves patterns.
 paths:
   - "**/*.py"
   - "**/*.pyi"

package/rules/python/security.md

@@ -1,9 +1,5 @@
-<!--
-rules/python/security.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct python security rule. Applies to files matching **/*.py, **/*.pyi. Use when writing or reviewing python code that involves security.
 paths:
   - "**/*.py"
   - "**/*.pyi"

package/rules/python/testing.md

@@ -1,9 +1,5 @@
-<!--
-rules/python/testing.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct python testing rule. Applies to files matching **/*.py, **/*.pyi. Use when writing or reviewing python code that involves testing.
 paths:
   - "**/*.py"
   - "**/*.pyi"

package/rules/swift/coding-style.md

@@ -1,9 +1,5 @@
-<!--
-rules/swift/coding-style.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct swift coding style rule. Applies to files matching **/*.swift, **/Package.swift. Use when writing or reviewing swift code that involves coding style.
 paths:
   - "**/*.swift"
   - "**/Package.swift"

package/rules/swift/hooks.md

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

package/rules/swift/patterns.md

@@ -1,9 +1,5 @@
-<!--
-rules/swift/patterns.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct swift patterns rule. Applies to files matching **/*.swift, **/Package.swift. Use when writing or reviewing swift code that involves patterns.
 paths:
   - "**/*.swift"
   - "**/Package.swift"

package/rules/swift/security.md

@@ -1,9 +1,5 @@
-<!--
-rules/swift/security.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct swift security rule. Applies to files matching **/*.swift, **/Package.swift. Use when writing or reviewing swift code that involves security.
 paths:
   - "**/*.swift"
   - "**/Package.swift"

package/rules/swift/testing.md

@@ -1,9 +1,5 @@
-<!--
-rules/swift/testing.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct swift testing rule. Applies to files matching **/*.swift, **/Package.swift. Use when writing or reviewing swift code that involves testing.
 paths:
   - "**/*.swift"
   - "**/Package.swift"

package/rules/typescript/coding-style.md

@@ -1,9 +1,5 @@
-<!--
-rules/typescript/coding-style.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct typescript coding style rule. Applies to files matching **/*.ts, **/*.tsx, **/*.js, **/*.jsx. Use when writing or reviewing typescript code that involves coding style.
 paths:
   - "**/*.ts"
   - "**/*.tsx"

package/rules/typescript/hooks.md

@@ -1,9 +1,5 @@
-<!--
-rules/typescript/hooks.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct typescript hooks rule. Applies to files matching **/*.ts, **/*.tsx, **/*.js, **/*.jsx. Use when writing or reviewing typescript code that involves hooks.
 paths:
   - "**/*.ts"
   - "**/*.tsx"

package/rules/typescript/patterns.md

@@ -1,9 +1,5 @@
-<!--
-rules/typescript/patterns.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct typescript patterns rule. Applies to files matching **/*.ts, **/*.tsx, **/*.js, **/*.jsx. Use when writing or reviewing typescript code that involves patterns.
 paths:
   - "**/*.ts"
   - "**/*.tsx"

package/rules/typescript/security.md

@@ -1,9 +1,5 @@
-<!--
-rules/typescript/security.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct typescript security rule. Applies to files matching **/*.ts, **/*.tsx, **/*.js, **/*.jsx. Use when writing or reviewing typescript code that involves security.
 paths:
   - "**/*.ts"
   - "**/*.tsx"

package/rules/typescript/testing.md

@@ -1,9 +1,5 @@
-<!--
-rules/typescript/testing.md: <one-line purpose>
-
-<2–6 line summary.>
--->
 ---
+description: Construct typescript testing rule. Applies to files matching **/*.ts, **/*.tsx, **/*.js, **/*.jsx. Use when writing or reviewing typescript code that involves testing.
 paths:
   - "**/*.ts"
   - "**/*.tsx"

package/rules/web/coding-style.md

@@ -1,8 +1,6 @@
-<!--
-rules/web/coding-style.md: <one-line purpose>
-
-<2–6 line summary.>
--->
+---
+description: Construct web coding style rule. Use when writing or reviewing web code that involves coding style.
+---
 > This file extends [common/coding-style.md](../common/coding-style.md) with web-specific frontend content.
 
 # Web Coding Style

package/rules/web/design-quality.md

@@ -1,8 +1,6 @@
-<!--
-rules/web/design-quality.md: <one-line purpose>
-
-<2–6 line summary.>
--->
+---
+description: Construct web design quality rule. Use when writing or reviewing web code that involves design quality.
+---
 > This file extends [common/patterns.md](../common/patterns.md) with web-specific design-quality guidance.
 
 # Web Design Quality Standards

package/rules/web/hooks.md

@@ -1,8 +1,6 @@
-<!--
-rules/web/hooks.md: <one-line purpose>
-
-<2–6 line summary.>
--->
+---
+description: Prefer project-local tooling.
+---
 # Web Hooks
 
 ## Recommended PostToolUse Hooks

package/rules/web/patterns.md

@@ -1,8 +1,6 @@
-<!--
-rules/web/patterns.md: <one-line purpose>
-
-<2–6 line summary.>
--->
+---
+description: Construct web patterns rule. Use when writing or reviewing web code that involves patterns.
+---
 > This file extends [common/patterns.md](../common/patterns.md) with web-specific patterns.
 
 # Web Patterns

package/rules/web/performance.md

@@ -1,8 +1,6 @@
-<!--
-rules/web/performance.md: <one-line purpose>
-
-<2–6 line summary.>
--->
+---
+description: Construct web performance rule. Use when writing or reviewing web code that involves performance.
+---
 > This file extends [common/performance.md](../common/performance.md) with web-specific performance content.
 
 # Web Performance Rules

package/rules/web/security.md

@@ -1,8 +1,6 @@
-<!--
-rules/web/security.md: <one-line purpose>
-
-<2–6 line summary.>
--->
+---
+description: Construct web security rule. Use when writing or reviewing web code that involves security.
+---
 > This file extends [common/security.md](../common/security.md) with web-specific security content.
 
 # Web Security Rules

package/rules/web/testing.md

@@ -1,8 +1,6 @@
-<!--
-rules/web/testing.md: <one-line purpose>
-
-<2–6 line summary.>
--->
+---
+description: Construct web testing rule. Use when writing or reviewing web code that involves testing.
+---
 > This file extends [common/testing.md](../common/testing.md) with web-specific testing content.
 
 # Web Testing Rules

package/skills/ai/agent-dev.md

@@ -1,8 +1,7 @@
-<!--
-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
--->
+---
+name: ai-agent-dev
+description: Use this skill when building AI agents, tool-use systems, or multi-agent workflows.
+---
 # AI Agent Development
 
 Use this skill when building AI agents, tool-use systems, or multi-agent workflows.

package/skills/ai/llm-security.md

@@ -1,8 +1,7 @@
-<!--
-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
--->
+---
+name: ai-llm-security
+description: Use this skill when securing LLM-powered applications against prompt injection, data leakage, and misuse.
+---
 # LLM Security
 
 Use this skill when securing LLM-powered applications against prompt injection, data leakage, and misuse.

package/skills/ai/ml-ops.md

@@ -1,8 +1,7 @@
-<!--
-skills/ai/ml-ops.md (ML Operations (MLOps)) ```
-
-## The MLOps Lifecycle ```
--->
+---
+name: ai-ml-ops
+description: Patterns, anti-patterns, and reference guidance for ML Operations (MLOps). Use when the task involves ml operations (mlops).
+---
 # ML Operations (MLOps)
 
 ## The MLOps Lifecycle

package/skills/ai/orchestration-workflow.md

@@ -1,8 +1,7 @@
-<!--
-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
--->
+---
+name: ai-orchestration-workflow
+description: Use this skill when the request involves agent orchestration, phase transitions, task keys, handoff quality, workflow state, or project alignment.
+---
 # Construct Orchestration Workflow
 
 Use this skill when the request involves agent orchestration, phase transitions, task keys, handoff quality, workflow state, or project alignment.

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

@@ -1,8 +1,7 @@
-<!--
-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
--->
+---
+name: ai-prompt-and-eval
+description: Use this skill when designing prompts, evaluating model performance, or optimizing LLM behavior.
+---
 # Prompt Engineering and Evaluation
 
 Use this skill when designing prompts, evaluating model performance, or optimizing LLM behavior.

package/skills/ai/prompt-optimizer.md

@@ -1,9 +1,7 @@
-<!--
-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.
--->
+---
+name: ai-prompt-optimizer
+description: Closed-loop prompt auto-optimization guide. Use when the task matches the trigger conditions described in the body.
+---
 # Prompt Auto-Optimization Loop
 
 Construct's prompt improvement system uses telemetry traces and quality scores as the feedback signal, Claude as the optimizer, and the agent registry (`specialists/registry.json`) as the deployment layer. This is a closed loop: production data → failure analysis → improved prompt → staging → promotion.

package/skills/ai/rag-system.md

@@ -1,8 +1,7 @@
-<!--
-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
--->
+---
+name: ai-rag-system
+description: Use this skill when building retrieval-augmented generation pipelines, vector search, or knowledge-grounded AI systems.
+---
 # RAG System Design
 
 Use this skill when building retrieval-augmented generation pipelines, vector search, or knowledge-grounded AI systems.

package/skills/architecture/api-design.md

@@ -1,8 +1,7 @@
-<!--
-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
--->
+---
+name: architecture-api-design
+description: Use this skill when designing REST, GraphQL, or gRPC APIs.
+---
 # API Design
 
 Use this skill when designing REST, GraphQL, or gRPC APIs.

package/skills/architecture/caching.md

@@ -1,8 +1,7 @@
-<!--
-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
--->
+---
+name: architecture-caching
+description: Use this skill when designing caching strategies for applications, APIs, or infrastructure.
+---
 # Caching
 
 Use this skill when designing caching strategies for applications, APIs, or infrastructure.

package/skills/architecture/cloud-native.md

@@ -1,8 +1,7 @@
-<!--
-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
--->
+---
+name: architecture-cloud-native
+description: Use this skill when designing containerized, orchestrated, or microservice-based systems.
+---
 # Cloud-Native Architecture
 
 Use this skill when designing containerized, orchestrated, or microservice-based systems.

package/skills/architecture/message-queue.md

@@ -1,8 +1,7 @@
-<!--
-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
--->
+---
+name: architecture-message-queue
+description: Use this skill when designing asynchronous communication, event-driven systems, or message-based integrations.
+---
 # Message Queues and Event-Driven Architecture
 
 Use this skill when designing asynchronous communication, event-driven systems, or message-based integrations.

package/skills/architecture/security-arch.md

@@ -1,8 +1,7 @@
-<!--
-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
--->
+---
+name: architecture-security-arch
+description: Use this skill when designing authentication, authorization, network security, or zero-trust architectures.
+---
 # Security Architecture
 
 Use this skill when designing authentication, authorization, network security, or zero-trust architectures.

package/skills/compliance/ai-disclosure.md

@@ -1,8 +1,7 @@
-<!--
-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.
--->
+---
+name: compliance-ai-disclosure
+description: Use this skill when reviewing AI features for disclosure requirements, transparency obligations, or emerging AI regulation compliance.
+---
 # AI Disclosure
 
 Use this skill when reviewing AI features for disclosure requirements, transparency obligations, or emerging AI regulation compliance.

package/skills/compliance/data-privacy.md

@@ -1,8 +1,7 @@
-<!--
-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.
--->
+---
+name: compliance-data-privacy
+description: Use this skill when reviewing data collection, storage, processing, or retention for privacy regulation compliance.
+---
 # Data Privacy
 
 Use this skill when reviewing data collection, storage, processing, or retention for privacy regulation compliance.