@byrde/cursor 0.1.1

package/assets/rules/init.mdc

@@ -0,0 +1,26 @@
+---
+alwaysApply: false
+description: Lightweight init fallback that points users to the CLI installer.
+---
+
+## Purpose
+
+This rule no longer runs the old embedded initialization conversation. Its job is only to preserve discoverability when a user reaches for `@init.mdc` directly.
+
+## Behavior
+
+1. **If workflow assets are missing**
+   - Instruct the user to run:
+     ```bash
+     npx @byrde/cursor init
+     ```
+   - Explain that the CLI installs rules, agents, templates, project config, and starter docs.
+
+2. **If workflow assets are installed but docs are still missing or in template mode**
+   - Explain that `.cursor/rules/global.mdc` now handles initialization automatically through the normal `/planner` then `/architect` flow.
+   - Point the user back to the regular chat flow instead of starting a separate embedded init conversation here.
+
+3. **Do not run legacy init scaffolding from this rule**
+   - No banners
+   - No persona handoff script
+   - No embedded planning or scaffolding sequence

package/assets/templates/backlog.md

@@ -0,0 +1,18 @@
+# Project Backlog
+
+| Epic | Priority | Task Description | Acceptance Criteria | Status | Prototype | Notes |
+| :--- | :--- | :--- | :--- | :--- | :--- | :--- |
+| **[Epic from Key Features]** | 1000 | [Task Title or User Story] | [Verifiable criteria for completion] | `TODO` |  | [Dependencies, context, testability considerations] |
+| **[Epic from Key Features]** | 1000 | [Task Title or User Story] | [Verifiable criteria for completion] | `TODO` |  | [Dependencies, context, testability considerations] |
+
+## Column Guide
+
+- **Priority**: Lower numbers sort earlier in the backlog (`1` before `2`). Use `1000` as an unprioritized default. In GitHub Project (v2) mode, this mirrors the Project **Priority** field.
+- **Status**: Must follow `TODO` → `In Progress` → `Ready to Test` → `Complete`. In GitHub Project (v2) mode, this mirrors the Project **Status** field.
+- **Epic**: In GitHub mode, epics are represented by **milestones** on issues.
+- **Prototype**: Maintained by prototyping workflow. Leave empty for new tasks. When prototype exists: `prototypes/[slug].[ext]` + brief findings.
+- **Notes**: Include testability considerations for non-trivial verification:
+  - If feature involves long-running processes, note start/verify/stop pattern needed
+  - If feature requires user interaction for testing, note the handoff scenario
+  - If verification is straightforward, no note needed
+  - Prefer pointing at the per-feature file under `docs/testability/` (e.g. `010-feature-slug.md`) when verification is non-trivial

package/assets/templates/design.md

@@ -0,0 +1,25 @@
+# Domain-Driven Design (DDD) Strategy
+
+### 1. Ubiquitous Language Glossary
+| Term | Definition | Aliases |
+| :--- | :--- | :--- |
+| **[Term]** | [Definition of the term within this specific domain.] | [Any synonyms or aliases?] |
+| **[Term]** | [Definition of the term within this specific domain.] | [Any synonyms or aliases?] |
+
+### 2. Core Domain and Bounded Context
+* **Core Domain:** The central and most important part of the software's business logic.
+    * *[Describe the single, most critical part of your business logic that gives you a competitive advantage.]*
+
+* **Bounded Contexts:** The distinct areas of the application with their own models and language.
+    * - **[Context Name]:** [Briefly describe the responsibility of this context and the language used within it.]
+    * - **[Context Name]:** [Briefly describe the responsibility of this context and the language used within it.]
+    * *[Add more contexts as needed]*
+
+### 3. Aggregates
+* A cluster of associated objects that we treat as a single unit for the purpose of data changes. *(Copy and paste the template below for each aggregate you identify).*
+
+* **[Aggregate Name] Aggregate**
+    * **Aggregate Root:** `[Root Entity Name]`
+    * **Entities:** `[List of other entities within the aggregate boundary]`
+    * **Value Objects:** `[List of value objects within the aggregate]`
+    * **Description:** `[Explain the aggregate's purpose and the business rules (invariants) it enforces.]`

package/assets/templates/overview.md

@@ -0,0 +1,38 @@
+# Software Development Project: [Project Name]
+
+## Overview
+
+### 1. Project Name
+* **[Your Project Name]**
+
+### 2. Project Description
+* A brief, high-level summary of the project. What is it? What does it do?
+    * *[Enter a one or two-sentence summary of the project's purpose and functionality.]*
+
+### 3. Project Vision
+* The long-term vision and ultimate goal of the project. What impact will it have?
+    * *[Describe the ultimate goal and the positive impact the project will have in the long term.]*
+
+### 4. Problem Statement
+* A clear and concise description of the problem this project aims to solve.
+    * *[Clearly define the problem, need, or pain point this project is intended to solve.]*
+
+### 5. Target Audience
+* A detailed description of the primary and secondary users of this software.
+    * **Primary Audience:** *[Describe the primary user group, including key demographics or characteristics.]*
+    * **Secondary Audience:** *[Describe any secondary user groups that will also use or be impacted by the software.]*
+
+### 6. Key Features
+* A list of the most important features and functionalities of the software. These will be considered the epics when filling out the backlog, take special care filling them out.
+    * - **[Feature Name]:** [Brief description of the feature.]
+    * - **[Feature Name]:** [Brief description of the feature.]
+    * - **[Feature Name]:** [Brief description of the feature.]
+    * *[Add more features as needed]*
+
+### 7. Technology Stack
+* A list of the technologies, frameworks, and platforms that will be used to build the project.
+    * **Frontend:** *[e.g., React, Vue, Angular, SvelteKit, iOS/Swift, Android/Kotlin]*
+    * **Backend:** *[e.g., Node.js, Python/Django, Go, Rust, Java/Spring]*
+    * **Database:** *[e.g., PostgreSQL, MongoDB, MySQL, SQLite, Redis]*
+    * **Authentication:** *[e.g., OAuth 2.0, JWT, Auth0, NextAuth, Firebase Auth]*
+    * **Deployment:** *[e.g., Docker, Vercel, AWS, Google Cloud, Azure]*

package/assets/templates/testability/README.md

@@ -0,0 +1,102 @@
+# Testability index
+
+Record how AI verifies each feature using shell commands. Prefer **one markdown file per feature** in this directory.
+
+In repositories that use Byrde’s GitHub Actions layout, the mandatory baseline is the **`build-and-test`** job. **`architect-review`** and **`feature-verification`** are additional visible checks that always run lightweight documentation verification and are not release gates.
+
+## Naming
+
+Use `{FEATURE_NUMBER}-{BRIEF_DESCRIPTION}.md` (for example `001-cli-auth.md`). `FEATURE_NUMBER` is a stable project-local identifier (often zero-padded or backlog-derived). `BRIEF_DESCRIPTION` is a short kebab-case slug.
+
+Optionally keep this `README.md` as a short index that links to active feature files.
+
+## What to capture (per feature file)
+
+Use the sections below as a checklist; omit sections that do not apply.
+
+### Quick entry
+
+| Feature | Verification command | Type |
+| :--- | :--- | :--- |
+| [Feature name] | `[shell command]` | Standard |
+| [Feature name] | See Long-Running section below | Long-running |
+| [Feature name] | See User-in-the-loop section below | User action required |
+
+## Standard verifications
+
+### [Feature name]
+
+```bash
+# Command to verify feature
+[command with arguments]
+```
+
+**Expected output:** [What success looks like]
+
+## Long-running process verifications
+
+For services, servers, or processes that do not exit immediately.
+
+### [Feature name]
+
+**Start:**
+
+```bash
+timeout 30 ./start-service &
+```
+
+**Verify:**
+
+```bash
+curl -f http://localhost:8080/health
+```
+
+**Stop:**
+
+```bash
+kill %1
+```
+
+**Notes:** [Special considerations]
+
+## User-in-the-loop verifications
+
+For OAuth, hardware, visual checks, etc.
+
+### [Feature name]
+
+**AI setup:**
+
+```bash
+[setup commands]
+```
+
+**User action required:**
+
+> [What the user must do]
+
+**AI verification** (after the user confirms):
+
+```bash
+[verification commands]
+```
+
+**Expected result:** [Success criteria]
+
+## Environment setup
+
+### Prerequisites
+
+- [Dependency]
+
+### Before testing
+
+```bash
+[setup]
+```
+
+### Cleanup
+
+```bash
+[cleanup]
+```