@geraldmaron/construct 1.0.14 → 1.0.15

package/rules/common/development-workflow.md

@@ -1,32 +0,0 @@
-<!--
-rules/common/development-workflow.md: feature implementation pipeline.
-
-Defines the research-plan-TDD-review-commit workflow that runs before
-git operations. References testing.md, code-review.md, git-workflow.md.
--->
-# Development Workflow
-
-## Feature Implementation Workflow
-
-0. **Research & Reuse** _(mandatory before any new implementation or artifact)_
-   - **Search existing code first:** Look for existing implementations, templates, and patterns before writing anything new.
-   - **Search existing artifacts:** Before authoring a doc, rule, template, strategy, PRD, ADR, or RFC, audit what already exists. See [review-before-change.md](review-before-change.md) for the audit checklist. Extend or supersede; do not duplicate.
-   - **Check docs:** Confirm API behavior, package usage, and version-specific details before implementing.
-   - **Check package registries:** npm, PyPI, crates.io before writing utility code.
-   - Prefer adopting a proven approach over writing net-new code.
-
-1. **Plan** - Break into phases; identify dependencies and risks.
-
-2. **TDD** - Write tests first (RED), implement (GREEN), refactor (IMPROVE). See [testing.md](testing.md).
-
-3. **Code Review** - Review immediately after writing. See [code-review.md](code-review.md).
-
-3.5. **Docs** _(mandatory for any user-facing change)_
-   - If you added or changed a CLI command, API endpoint, config option, or architecture boundary: update `docs/concepts/architecture.md` and create or update the relevant `docs/cookbook/` recipe.
-   - If you added a CLI command, ensure the cookbook index links to a recipe for it.
-   - Run `construct docs:update` to regenerate AUTO-managed regions.
-   - A change is not DONE if a user-facing capability exists with no documentation.
-
-4. **Commit** - Conventional commits format. See [git-workflow.md](git-workflow.md).
-
-5. **Pre-Review Checks** - CI passing, conflicts resolved, branch synced.

package/rules/common/performance.md

@@ -1,55 +0,0 @@
-<!--
-rules/common/performance.md: model-agnostic performance and context management rules.
-
-Defines model selection tiers, context window management heuristics,
-and build troubleshooting steps. No platform-specific tool names or config paths.
--->
-# Performance Optimization
-
-## Model Selection Strategy
-
-**Fast tier** (small/cheap models):
-- Lightweight agents with frequent invocation
-- Pair programming and code generation
-- Worker agents in multi-agent systems
-
-**Standard tier** (mid-range models):
-- Main development work
-- Orchestrating multi-agent workflows
-- Complex coding tasks
-
-**Reasoning tier** (large/frontier models):
-- Complex architectural decisions
-- Maximum reasoning requirements
-- Research and analysis tasks
-
-## Context Window Management
-
-Avoid last 20% of context window for:
-- Large-scale refactoring
-- Feature implementation spanning multiple files
-- Debugging complex interactions
-
-Prefer this retrieval ladder before loading more context:
-1. Targeted search to narrow candidate files
-2. Targeted reads (aim for <400 lines)
-3. Parallel reads for the minimum necessary file set
-4. Summarize to a context artifact before broad re-exploration
-
-Heuristics:
-- Re-reading the same file multiple times without a state change is a retrieval smell.
-- Large reads should be reserved for files where local structure matters more than symbol search.
-- Use workflow/context artifacts as cached state instead of rediscovering background repeatedly.
-
-Lower context sensitivity tasks:
-- Single-file edits
-- Independent utility creation
-- Documentation updates
-- Simple bug fixes
-
-## Build Troubleshooting
-
-If build fails:
-1. Analyze error messages
-2. Fix incrementally
-3. Verify after each fix