Skip to content

Bootstrap repo-setup with configuration system and documentation standard#1

Merged
virtualian merged 8 commits into
mainfrom
create-scaffold
Nov 18, 2025
Merged

Bootstrap repo-setup with configuration system and documentation standard#1
virtualian merged 8 commits into
mainfrom
create-scaffold

Conversation

@virtualian
Copy link
Copy Markdown
Owner

Summary

This PR establishes the foundational configuration system for repo-setup and creates the first universal standard.

Key Changes

  1. Universal Documentation Standard (prompts/user-documentation-standard.md)

    • Mandates Diataxis four-quadrant framework for all projects
    • Mandates Role-First organization for multi-audience documentation
    • Mandates documentation-code parity for CLI/API projects
    • Technology-agnostic (principles, not tools)
  2. Project Bootstrap

    • Added CLAUDE.md with two-layer configuration references
    • Created prompts/ directory with project-level standards
    • Established directory structure (docs/, plans/, research/, examples/)
  3. Configuration Examples

    • User-level examples (git workflow, testing, MCP usage standards)
    • Project-level examples (comprehensive implementations)
    • Standard definition framework
  4. Archive Original Spec

    • Moved docs/functional-specification.md to research/functional-specification-original.md
    • Preserves historical analysis and patterns
    • Clears path for Product Requirements Document

Key Insights

  • Diataxis IS a standard - It prescribes method (content classification), not technology
  • Role-First and Diataxis are orthogonal - They compose as a matrix (content type × audience)
  • PRD needed, not functional spec - Product owner needs WHAT/WHY, not implementation HOW

Next Steps

After merge:

  • Draft Product Requirements Document
  • Extract patterns from original spec to research docs
  • Define initialization and validation requirements

🤖 Generated with Claude Code

virtualian and others added 8 commits November 17, 2025 10:18
- Remove project type classification (unified standards for all repos)
- Remove excessive SemVer from file naming (Git tracks versions)
- Rename to functional-specification.md (no version suffix)
- Simplify naming: prj-git-workflow-standard.md (not v1.0.0)
- All repos get same three standards: git workflow, testing, MCP usage
- Optional project-specific standards can be added as needed
- Collect real-world configuration examples from active projects
- Add user-level config examples (CLAUDE.md, prompts, helper scripts)
- Add project-level examples:
  - Comprehensive: gainfunction, marrbox, specverse-app-portal
  - Simplified: npm-protect (with doc parity protocol)
- Document Documentation Parity Protocol in functional spec
  - Optional standard for CLI/tooling projects
  - Mandatory doc updates when scripts change
  - Pre-commit checklist and detection script
  - Script-level documentation parity requirement
- Add examples/README.md documenting all patterns
- Remove specverse-lang and scoremyclays (no unique patterns)

Examples now provide reference implementations for new projects.
- Add .gitignore (macOS, editors, logs, env files)
- Add CLAUDE.md following unified standards approach
- Create prompts/ with three standard project prompts
  - prj-git-workflow-standard.md
  - prj-testing-standard.md
  - prj-mcp-usage-standard.md
- Create plans/ directory for implementation planning
- Update README.md with comprehensive project overview

Repo now "eats its own dog food" - demonstrates the
configuration system it documents.
- Create prj-documentation-standard.md
  - Define directory organization (docs/, examples/, plans/, prompts/)
  - Document standards for each doc type
  - Quality requirements and anti-patterns
  - Maintenance workflows
- Add startup imperatives to CLAUDE.md
  - Read all standards in ./prompts/ on startup
  - Simple, maintenance-free approach (no file enumeration)
- Update CLAUDE.md to reference documentation standard
- Update functional spec optional standards list

This repo now has explicit rules for documentation organization
and ensures project-level prompts are loaded when work begins.
- Add prompts/user-documentation-standard.md with Diataxis framework
  - Mandates four-quadrant content classification (Tutorial/How-To/Reference/Explanation)
  - Mandates Role-First organization for multi-audience projects
  - Mandates documentation-code parity for CLI/API projects
  - Technology-agnostic (no MkDocs/Material specifics)

- Move functional spec to research/functional-specification-original.md
  - Preserves historical analysis and patterns
  - Clears docs/ for upcoming PRD

- Add examples/user-level/prompts/user-standard-for-standards.md
  - Defines what constitutes a standard (binding constraint on method)
  - Establishes standard-writing rules

Key insight: Diataxis IS a standard because it prescribes method (content classification), not technology. Role-First and Diataxis are orthogonal concerns that compose together.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@virtualian virtualian merged commit f8166ef into main Nov 18, 2025
@virtualian virtualian deleted the create-scaffold branch November 18, 2025 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant