@wildorder/nightshift 0.1.0 → 0.3.0

package/templates/AGENTS.md

@@ -0,0 +1,29 @@
+<!-- BEGIN UNIVERSAL — source: {{UNIVERSAL_SOURCE}} -->
+{{UNIVERSAL_DIRECTIVES}}
+<!-- END UNIVERSAL -->
+
+---
+
+## Project: {{PROJECT_NAME}}
+
+See `docs/vision.md` for the full product vision.
+See `docs/programs/` for program plans and manifests.
+See `tasks/{program-id}/` for workstream specs.
+
+### Tech Stack
+
+{{STACK}}
+
+### Product
+
+{{DESCRIPTION}}
+
+### Conventions
+
+[Document project-specific module structure, naming, IDs, validation, testing, and delivery conventions.]
+
+### Dependency Versions (pin these)
+
+| Package | Version |
+|---------|---------|
+{{DEPENDENCY_ROWS}}

package/templates/CLAUDE.md

@@ -0,0 +1,7 @@
+# Agent Directives
+
+The canonical agent directives, project context, conventions, and constraints for
+{{PROJECT_NAME}} live in **`AGENTS.md`**.
+
+**Read `AGENTS.md` now and follow it.** Do not maintain instructions in this file—
+update `AGENTS.md` instead to keep a single source of truth.

package/templates/universal-directives.md

@@ -0,0 +1,50 @@
+# Agent Directives: Universal
+
+These directives apply to every agent working in this repository, regardless
+of provider or harness.
+
+## Scope and depth
+
+1. SPEC-FIRST: When a workstream spec exists under `tasks/`, read it before
+   implementing. Do not invent architecture that contradicts the spec or
+   `docs/vision.md`. If the spec is ambiguous, ask — do not guess.
+
+2. ROOT CAUSE OVER SYMPTOM: Prefer the smallest diff that fully solves the
+   root cause, not the smallest diff that makes symptoms disappear. When the
+   proper fix is out of scope, say so explicitly and propose it as a
+   follow-up instead of silently shipping a band-aid.
+
+3. STRUCTURAL FIXES STAY IN SCOPE: If architecture is flawed, state is
+   duplicated, or patterns are inconsistent inside the files the task already
+   touches, fix it. Do not expand into unrelated modules without asking. On
+   question-only or review-only tasks, answer — do not rewrite code unless
+   asked.
+
+## Verification
+
+4. VERIFY BEFORE CLAIMING COMPLETION: A successful file write proves nothing
+   about correctness. Before reporting a task complete, run the project's
+   configured build, type-check, test, and lint commands and fix every
+   resulting error. If one of those commands is not configured, state that
+   explicitly instead of claiming it passed.
+
+## Edit safety
+
+5. READ BEFORE EDITING: Read a file before modifying it, and re-read any file
+   you have not seen recently in a long session before editing it again.
+
+6. EXHAUSTIVE RENAMES: When renaming any function, type, or variable, search
+   for direct references, type-level references, string literals, dynamic
+   imports, re-exports, and test files. Do not assume one search pass caught
+   everything.
+
+## Large tasks
+
+7. WORK IN VERIFIABLE PHASES: Break multi-file work into phases that each
+   pass verification on their own. In interactive sessions, pause between
+   phases for review; in automated pipeline runs, complete and verify each
+   phase before starting the next.
+
+8. PARALLELIZE INDEPENDENT WORK: When the harness supports sub-agents and the
+   task spans many independent files, split the work rather than degrading a
+   single context; keep tightly coupled changes together.

package/templates/vision.md

@@ -0,0 +1,46 @@
+# {{PROJECT_NAME}} — Vision Document
+
+## What Is {{PROJECT_NAME}}?
+[One paragraph: what the product is and why it exists.]
+
+**One-liner:** {{DESCRIPTION}}
+
+## The Problem
+[What pain point does this solve? Who has this problem?]
+
+## The Solution
+[High-level description of the approach.]
+
+## Architecture
+[System architecture diagram or description. ASCII art is fine.]
+
+## Core Concepts
+[Key abstractions, entities, or domain concepts.]
+
+## API Surface
+[Public-facing interfaces: SDK methods, REST endpoints, CLI commands, etc.]
+
+## Data Model
+[Key entities and their relationships.]
+
+## Target Users
+[Primary and secondary personas.]
+
+## Technology Stack
+
+**Primary stack:** {{STACK}}
+
+| Layer | Choice | Rationale |
+|-------|--------|-----------|
+| [Layer] | [Technology] | [Why it fits] |
+
+## Scope: Phase 1
+
+**Build:**
+- [Phase 1 deliverable]
+
+**Do not build in Phase 1:**
+- [Explicitly deferred item]
+
+## Scope: Phase 2+
+[Brief notes on future direction—enough to inform architectural decisions.]