@jakkrichm/create-nexus-devflow 2.0.6 → 2.0.8

package/template/devflow/context/coding-standards.md

@@ -1,19 +1,27 @@
-# Coding Standards & Guidelines
+# Coding Standards
 
-General engineering standards for code, tests, and documentation.
+> Project conventions and rules to follow during development.
+> Run `/onboard` (or `/adopt` for existing codebases) to tune these standards to your specific stack.
 
-## Code Quality
+## Architecture and Conventions
 
-- Write clear, self-documenting code.
-- Avoid unnecessary complexity (prefer simple solutions over indirect abstractions).
-- Maintain type safety and static validation across module boundaries.
+- Write clean, modular, and maintainable code with clear single responsibilities.
+- Prefer TypeScript and explicit interfaces where available.
+- Keep dependencies lean and justified.
 
-## Testing & Verification
+## Code Organization & Style
 
-- Every change in `/40-Implement` must be verified in `/50-Verify`.
-- Prefer test-driven evidence and automated scripts where applicable.
+- Structure source code following framework-native conventions.
+- Keep functions focused and avoid deeply nested logic.
+- Use consistent naming conventions (camelCase for functions/variables, PascalCase for components/types).
 
-## Git & Commits
+## Error Handling & Security
 
-- Commit messages follow imperative summary format.
-- Create small, reviewed, and self-contained commits.
+- Handle errors explicitly and provide meaningful error messages.
+- Never hardcode credentials, secrets, or API keys in source code.
+- Sanitize and validate all user inputs.
+
+## Testing & Quality
+
+- Follow the TDD workflow for behavior-changing code units.
+- Run tests and linting before completing features or fixes.

package/template/devflow/context/current-stage.md

@@ -3,4 +3,5 @@
 - **Active Discovery ID**: None
 - **Active Running ID**: None
 - **Current Stage**: Idle
-- **Last Updated**: 2026-08-17
+- **Last Completed Run**: None
+- **Last Updated**: -

package/template/devflow/context/findings.md

@@ -1,13 +1,9 @@
-# Audit Findings Ledger
+# Findings Ledger
 
-Summary of audit findings, quality checks, security bugs, and debt tracked across DevFlow runs.
+> Review findings raised by `/security-review` or QA audits.
+> Resolved findings are tracked with durable IDs.
 
-## Open Findings
+- **Total Open P0/P1**: 0
+- **Total Tracked**: 0
 
-| ID | Severity | Category | Title | Discovered Run | Status |
-| :- | :--- | :--- | :--- | :--- | :--- |
-
-## Resolved Findings
-
-| ID | Severity | Category | Title | Resolved Run | Date |
-| :- | :--- | :--- | :--- | :--- | :--- |
+_No findings recorded._

package/template/devflow/context/project-overview.md

@@ -1,20 +1,19 @@
 # Project Overview
 
-Primary source of truth for the project context, architecture, tech stack, and active DevFlow stage status.
+> **DevFlow Context Source of Truth.**
+> Single AI-facing source of truth for project architecture, stack, and shipped capabilities.
+> Run `/onboard` (for fresh projects) or `/adopt` (for existing codebases) to populate this file automatically.
 
-## Application Summary
+## 1. Project Summary
 
-- **Project Name**: [Project Name]
-- **Goal**: [Project Goal Description]
-- **Target Audience**: [Target Users]
+- **Name**: [Project Name]
+- **Description**: [One-line summary of project purpose]
+- **Primary Stack**: [Framework / Language / Runtime]
 
-## Tech Stack
+## 2. Architecture & Modules
 
-- **Frontend**: [Framework / Language]
-- **Backend**: [Framework / Database]
-- **Deployment**: [Platform / Infrastructure]
+- `src/` - Core application source code
 
-## DevFlow Workspaces
+## 3. Shipped Capabilities
 
-- **Active Discovery ID**: None
-- **Active Running ID**: None
+- None recorded yet. Run `/onboard` or `/adopt` to initialize.