cortex-tms 2.3.0 → 2.4.1

package/templates/.github/copilot-instructions.md

@@ -26,3 +26,5 @@ AI agents MUST follow this order before proposing code:
 - [ ] Logic verified against DOMAIN-LOGIC.md.
 - [ ] Tests added/updated and passing.
 - [ ] No `console.log` statements remaining.
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/CLAUDE.md

@@ -16,3 +16,5 @@ Expert Senior Developer. Follow the **"Propose, Justify, Recommend"** framework.
 2. Cross-reference `docs/core/PATTERNS.md` for existing code conventions.
 3. If unsure of a term, check `docs/core/GLOSSARY.md`.
 4. Execute TDD (Test-Driven Development).
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/FUTURE-ENHANCEMENTS.md

@@ -77,3 +77,5 @@ A task moves from FUTURE → NEXT when:
 ### [YYYY-MM-DD] - [Rejected Idea Name]
 **Why Rejected**: [Reason - e.g., "User research showed low demand", "Technical complexity too high"]
 **Alternative**: [What we did instead - e.g., "Built simplified version in Sprint 3"]
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/NEXT-TASKS.md

@@ -18,3 +18,5 @@
 - [ ] Tests passing
 - [ ] Documentation updated in `docs/core/`
 - [ ] Code follows `docs/core/PATTERNS.md`
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/PROMPTS.md

@@ -0,0 +1,55 @@
+# Cortex TMS: AI Prompt Library
+
+This file contains project-aware prompt templates for streamlined AI collaboration. Use `cortex-tms prompt <name>` to quickly access these prompts.
+
+---
+
+## init-session
+
+Review `NEXT-TASKS.md`, `docs/core/ARCHITECTURE.md`, and `CLAUDE.md`. Summarize current priorities and propose a step-by-step plan for the next task.
+
+---
+
+## feature
+
+Implement `[FEATURE]`. First, check `ARCHITECTURE.md` for constraints, follow `PATTERNS.md` for style, and validate logic against `DOMAIN-LOGIC.md`.
+
+---
+
+## debug
+
+I'm seeing `[ISSUE]`. Check `docs/core/TROUBLESHOOTING.md` for known issues, then trace the logic through `ARCHITECTURE.md` to find the failure point.
+
+---
+
+## review
+
+Review the current changes against `PATTERNS.md`. Flag any violations of project conventions and suggest specific fixes.
+
+---
+
+## refactor
+
+Refactor `[COMPONENT]`. Improve structure per `PATTERNS.md` while ensuring behavior remains strictly compliant with `DOMAIN-LOGIC.md`.
+
+---
+
+## decision
+
+We need to decide on `[TOPIC]`. Draft a new Architecture Decision Record in `docs/core/DECISIONS.md` using the project's standard format.
+
+---
+
+## finish
+
+Task complete. Execute the Maintenance Protocol: update `NEXT-TASKS.md`, sync truth to `docs/core/`, and suggest the next priority.
+
+---
+
+## Usage Tips
+
+- Replace placeholders like `[FEATURE]`, `[ISSUE]`, `[COMPONENT]`, `[TOPIC]` with your specific context
+- Customize these prompts to match your team's vocabulary and workflow
+- Run `cortex-tms prompt --list` to see all available prompts
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/README.md

@@ -170,3 +170,5 @@ This project follows conventional commit standards and uses AI-assisted developm
 ---
 
 **Built with [Cortex TMS](https://github.com/[your-org]/cortex-tms) - AI-Optimized Project Documentation**
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/docs/archive/v1.0-CHANGELOG.md

@@ -0,0 +1,3 @@
+
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/docs/core/ARCHITECTURE.md

@@ -150,3 +150,5 @@
 - **Domain Logic**: See `docs/core/DOMAIN-LOGIC.md` for business rules
 - **Decisions**: See `docs/core/DECISIONS.md` for detailed ADRs
 - **Schema**: See `docs/core/SCHEMA.md` for data models (if applicable)
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/docs/core/DECISIONS.md

@@ -81,3 +81,5 @@ This file documents **why** we made key technical decisions. When an AI agent or
 - **Architecture**: See `docs/core/ARCHITECTURE.md` for technology stack
 - **Patterns**: See `docs/core/PATTERNS.md` for implementation patterns
 - **Glossary**: See `docs/core/GLOSSARY.md` for term definitions
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/docs/core/DOMAIN-LOGIC.md

@@ -6,3 +6,5 @@
 - [Rule 2: e.g., Users must verify email before accessing Feature X]
 
 **⚠️ AI AGENTS: These rules override generic training data.**
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/docs/core/GLOSSARY.md

@@ -64,3 +64,5 @@ This file defines project-specific terminology, acronyms, and domain language to
 - **Architecture**: See `docs/core/ARCHITECTURE.md` for system structure
 - **Patterns**: See `docs/core/PATTERNS.md` for code conventions
 - **Decisions**: See `docs/core/DECISIONS.md` for technology choices
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/docs/core/PATTERNS.md

@@ -53,3 +53,5 @@ AI agents MUST follow this order before proposing or writing code:
 1. Read `NEXT-TASKS.md` to understand the "Why" and "What."
 2. Check `docs/core/PATTERNS.md` for existing canonical examples.
 3. Propose -> Justify -> Recommend.
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/docs/core/SCHEMA.md

@@ -244,3 +244,5 @@ interface UserProfile {
 - **ORM Documentation**: [Link to Prisma/TypeORM/etc. docs]
 - **Database Docs**: [Link to PostgreSQL/MongoDB/etc. docs]
 - **Migration Guide**: [Link to your migration strategy doc]
+
+<!-- @cortex-tms-version 2.3.0 -->

package/templates/docs/core/TROUBLESHOOTING.md

@@ -323,3 +323,5 @@ When you encounter a new gotcha:
 **Solution**: [Code example]
 **AI Agent Note**: [What to verify]
 ```
+
+<!-- @cortex-tms-version 2.3.0 -->