@productbrain/cli 0.1.0-beta.7 → 0.1.0-beta.71

package/templates/archetypes/convention.md

@@ -0,0 +1,23 @@
+---
+name: chain-conventions
+description: "{{entry_count}} conventions derived from Chain decision and pattern entries"
+autoApply: true
+level: core
+---
+
+# Chain-Derived Conventions
+
+These {{entry_count}} decision and pattern entries establish conventions for this workspace. Follow them unless you have a decision on the Chain that says otherwise.
+
+**Convention entries:** {{entry_ids}}
+
+{{convention_summary}}
+
+## What this means
+
+- Conventions are established patterns, not suggestions. They reduce decision fatigue.
+- Before inventing a new pattern, search the Chain — it may already be a convention.
+- Run `pb get <ID>` to understand the rationale behind a convention before deviating.
+- If you must deviate, capture a DEC on the Chain explaining the new direction.
+
+**Source entries (names):** {{entry_names}}

package/templates/archetypes/policy.md

@@ -0,0 +1,23 @@
+---
+name: chain-policies
+description: "{{entry_count}} operational policies derived from Chain policy and business-rule entries"
+autoApply: true
+level: core
+---
+
+# Chain-Derived Policies
+
+These {{entry_count}} policy and business-rule entries govern workflows and access in this workspace. Policies apply even when they are inconvenient.
+
+**Policy entries:** {{entry_ids}}
+
+{{policy_summary}}
+
+## What this means
+
+- Policies govern who can do what and under what conditions.
+- Security, auth, and access control policies are never optional.
+- Run `pb get <ID>` to read the full policy before implementing anything in its domain.
+- If a policy conflicts with a feature requirement, capture a TEN and escalate — do not quietly violate.
+
+**Source entries (names):** {{entry_names}}

package/templates/archetypes/quality-gate.md

@@ -0,0 +1,23 @@
+---
+name: chain-quality-gates
+description: "{{entry_count}} quality gates derived from Chain standard and business-rule entries"
+autoApply: true
+level: core
+---
+
+# Chain-Derived Quality Gates
+
+These {{entry_count}} standard and business-rule entries define quality gates that must pass before shipping. No exceptions without a documented reason on the Chain.
+
+**Quality gate entries:** {{entry_ids}}
+
+{{quality_summary}}
+
+## What this means
+
+- Quality gates are pass/fail. They are not approximate.
+- Run `npm run build` and `npm run test` before every push — always.
+- Run `pb get <ID>` to read the specific acceptance criteria for a quality gate.
+- If a gate cannot pass due to a legitimate constraint, capture a TEN before shipping.
+
+**Source entries (names):** {{entry_names}}

package/templates/archetypes/workflow.md

@@ -0,0 +1,23 @@
+---
+name: chain-workflows
+description: "{{entry_count}} required process flows derived from Chain flow entries"
+autoApply: true
+level: core
+---
+
+# Chain-Derived Workflows
+
+These {{entry_count}} flow entries define required processes for this workspace. If a workflow entry exists for a process you are about to execute, follow it.
+
+**Workflow entries:** {{entry_ids}}
+
+{{workflow_summary}}
+
+## What this means
+
+- Workflows define the correct sequence of steps for key processes.
+- Skipping a step is not the same as completing the workflow.
+- Run `pb get <ID>` to read the full workflow before executing the process it defines.
+- If the workflow is incomplete or outdated, capture a TEN — do not silently deviate.
+
+**Source entries (names):** {{entry_names}}

package/templates/general/code-integrity.md

@@ -0,0 +1,11 @@
+---
+name: code-integrity
+description: General code quality patterns
+level: core
+---
+
+# Code Integrity
+
+- Derive from the source of truth, don't duplicate
+- Handle errors at boundaries, not everywhere
+- Names should describe what, not how

package/templates/general/getting-started.md

@@ -0,0 +1,12 @@
+---
+name: getting-started
+description: Product Brain onboarding for new workspaces
+level: core
+---
+
+# Getting Started with Product Brain
+
+- Run `pb orient -b` to see your workspace state
+- Run `pb handshake` after changing rules or skills in `.productbrain/`
+- Rules go in `.productbrain/rules/`, skills go in `.productbrain/skills/`
+- The Chain is the single source of truth — use `pb get <ID>` to load any entry

package/templates/node-ts/code-integrity.md

@@ -0,0 +1,13 @@
+---
+name: code-integrity
+description: TypeScript code quality patterns
+level: core
+when_stack: typescript
+---
+
+# Code Integrity
+
+- Use strict TypeScript (`strict: true` in tsconfig)
+- Prefer `const` over `let`
+- Use explicit return types on exported functions
+- Handle errors at boundaries, not everywhere

package/templates/node-ts/testing.md

@@ -0,0 +1,12 @@
+---
+name: testing
+description: Testing standards for Node/TypeScript projects
+level: intermediate
+when_stack: typescript
+---
+
+# Testing Standards
+
+- Test behavior, not implementation
+- One assertion per test when possible
+- Use descriptive test names that read as specifications

package/templates/python/code-integrity.md

@@ -0,0 +1,13 @@
+---
+name: code-integrity
+description: Python code quality patterns
+level: core
+when_stack: python
+---
+
+# Code Integrity
+
+- Use type hints on function signatures
+- Prefer f-strings over .format()
+- Handle errors at boundaries, not everywhere
+- Use pathlib over os.path

package/templates/python/testing.md

@@ -0,0 +1,12 @@
+---
+name: testing
+description: Testing standards for Python projects
+level: intermediate
+when_stack: python
+---
+
+# Testing Standards
+
+- Test behavior, not implementation
+- Use pytest fixtures for shared setup
+- Use descriptive test names that read as specifications