colign — Prompt Files
Note: The Claude Code plugin lives in colign/plugin (separate repository). Prompt files were not fetchable from the main colign/colign repo. The CLAUDE.md and structural files below are the primary sources.
Excerpt 1: CLAUDE.md — Development Standards for Colign Contributors
# Colign
## Testing
- Always use `/tdd` skill when changing code — write tests first (RED → GREEN → REFACTOR)
- Unit tests required for all Go packages, target 80%+ coverage
- Auth/security code (auth, apitoken, oauth, middleware) targets 100% coverage
## Code Quality
- Always handle error returns. Never use `_, _ =` to discard errors — check or log them
- Logging: use `log/slog` (structured logging). Do not use `fmt.Println`, `log.Printf`, or third-party loggers
- Must pass golangci-lint (errcheck)
- commitlint: conventional commits format, subject must start lowercase
## Database
- Always invoke `/database-design:postgresql` skill before writing or modifying migration SQL
- Prefer `TEXT` over `VARCHAR(n)` — use `CHECK (LENGTH(col) <= n)` if limit needed
- Use `BIGINT GENERATED ALWAYS AS IDENTITY` — never `BIGSERIAL` or `SERIAL`
- Always add indexes on FK columns manually — PostgreSQL does not auto-index FKs
- Use `TIMESTAMPTZ`, never `TIMESTAMP` without timezone
Technique: Database convention-as-law — specific SQL anti-patterns are banned by name (BIGSERIAL, SERIAL, TIMESTAMP without TZ). This prevents a well-known class of PostgreSQL migration debt accumulated over time.
| Section | Required | Purpose |
|---------|:--------:|---------|
| **Problem** | Yes | Why is this change needed? |
| **Scope** | Yes | What specifically will change? |
| **Out of Scope** | No | What is explicitly NOT part of this? |
| **Approach** | No | Technical direction and rationale |
| **Acceptance Criteria** | Yes | Given/When/Then scenarios |
Technique: Required/optional schema enforcement — Problem, Scope, and Acceptance Criteria are required fields; Approach and Out of Scope are optional. This enforces minimum spec quality without over-prescribing format.
Excerpt 3: Plugin Skill Chain (from README)
onboard → explore → propose → plan → implement → complete
Technique: Contextual skill triggering — Skills trigger automatically by context ("implement the next task") or explicitly via /colign:implement. The skill chain mirrors the human review workflow stages, making it natural for agents to pick up where humans left off.
Prompting Techniques Summary
- Required schema enforcement — Problem/Scope/Acceptance Criteria required, others optional
- Two-layer spec architecture — Project Memory (strategic, stable) + Structured Proposal (tactical, per-change)
- Convention-as-law — SQL antipatterns banned by CLAUDE.md
- BDD Acceptance Criteria — Given/When/Then enforced as the test specification format
- TDD enforcement —
/tdd skill required before any code change (for Colign's own codebase)