@etus/bhono-app 0.1.1

package/templates/base/.claude/commands/ship.md

@@ -0,0 +1,262 @@
+---
+allowed-tools: Read, Edit, Write, Glob, Grep, Bash, Task, TodoWrite, SlashCommand
+argument-hint: [--no-tests] [--no-lint] [--no-docs] [--no-claude-md] [--no-readme] [--no-push]
+description: Automated commit/push workflow with quality checks and documentation updates
+skills: playwright-e2e-testing
+---
+
+# /ship - Automated Commit Workflow
+
+Fully automated workflow that runs quality checks, updates documentation, and commits/pushes changes.
+
+## Arguments Received
+
+```
+$ARGUMENTS
+```
+
+## Parse Flags
+
+!`echo "$ARGUMENTS" | grep -q "\-\-no-tests" && echo "SKIP_TESTS=true" || echo "SKIP_TESTS=false"`
+!`echo "$ARGUMENTS" | grep -q "\-\-no-lint" && echo "SKIP_LINT=true" || echo "SKIP_LINT=false"`
+!`echo "$ARGUMENTS" | grep -q "\-\-no-docs" && echo "SKIP_DOCS=true" || echo "SKIP_DOCS=false"`
+!`echo "$ARGUMENTS" | grep -q "\-\-no-claude-md" && echo "SKIP_CLAUDE_MD=true" || echo "SKIP_CLAUDE_MD=false"`
+!`echo "$ARGUMENTS" | grep -q "\-\-no-readme" && echo "SKIP_README=true" || echo "SKIP_README=false"`
+!`echo "$ARGUMENTS" | grep -q "\-\-no-push" && echo "SKIP_PUSH=true" || echo "SKIP_PUSH=false"`
+
+## Current Git Status
+
+!`git status --short`
+
+## Changed Files (Staged + Unstaged)
+
+!`git diff --name-only HEAD 2>/dev/null || git diff --name-only`
+
+## Recent Commits (for commit message style)
+
+!`git log --oneline -5`
+
+---
+
+## INSTRUCTIONS
+
+Execute this workflow in order. Use TodoWrite to track progress through each phase.
+
+### Phase 1: Information Gathering (Parallel Subagents)
+
+Launch 3 subagents IN PARALLEL using the Task tool:
+
+**Agent 1 - Change Analyzer:**
+
+```
+Analyze the git diff to understand what changed.
+Run: git diff --stat && git diff --name-only
+Categorize changes by:
+- Source code changes (apps/, packages/)
+- Test changes (tests/)
+- Config changes (*.json, *.yaml, etc.)
+- Documentation changes (docs/, *.md)
+Return a structured summary of what changed and the primary type of change (feat/fix/refactor/test/docs/chore).
+```
+
+**Agent 2 - CLAUDE.md and AGENTS.md Mapper:**
+
+```
+Run /prime first to understand the codebase.
+Given the changed files, identify which CLAUDE.md and AGENTS.md files need updating.
+Map changed source files to their nearest CLAUDE.md:
+- apps/edge/src/* → apps/edge/src/CLAUDE.md and apps/edge/src/AGENTS.md
+- packages/sdk-web/src/* → packages/sdk-web/src/CLAUDE.md and packages/sdk-web/src/AGENTS.md
+- etc.
+Also check if root CLAUDE.md and AGENTS.md needs updating (new packages, commands, key files).
+Return list of CLAUDE.md and AGENTS.md files that need updates.
+```
+
+**Agent 3 - Architecture Docs Mapper:**
+
+```
+Run /prime first to understand the codebase.
+Given the changed files, identify which architecture docs need updating:
+- Update the README.md if structural changes
+- Update the `docs/app_spec.txt` if structural changes
+- API endpoint changes → docs/architecture/api-catalog.md
+- New components/services → docs/architecture/c4-component.md
+- Container changes → docs/architecture/c4-container.md
+- Dependency changes → docs/architecture/dependencies.md
+- Major decisions → new ADR in docs/architecture/decisions/
+- Features updates → docs/features/
+- Data related changes → docs/data/
+- SDLC related changes → docs/sdlc/
+- Tech specs related changes → docs/tech-specs/
+- Runbooks related changes → docs/runbooks/
+Return list of architecture docs that need updates with reason.
+```
+
+Wait for all 3 agents to complete before proceeding.
+
+### Phase 2: Quality Checks (Sequential)
+
+**Skip this phase if --no-tests AND --no-lint are both set.**
+
+Execute sequentially (not parallel) to avoid file conflicts when fixing:
+
+#### Step 2.1: Tests (unless --no-tests)
+
+```bash
+pnpm run test
+```
+
+- If tests fail: Fix the failing tests, then rerun
+- Repeat until all tests pass
+- Maximum 3 fix attempts, then report and continue
+
+#### Step 2.2: Lint (unless --no-lint)
+
+```bash
+pnpm run lint
+```
+
+- If lint fails: Run `pnpm run lint --fix` first
+- For remaining errors: Fix manually, then rerun
+- Maximum 3 fix attempts, then report and continue
+
+#### Step 2.3: Typecheck (unless --no-lint)
+
+```bash
+pnpm run typecheck
+```
+
+- If typecheck fails: Fix type errors, then rerun
+- Maximum 3 fix attempts, then report and continue
+
+### Phase 3: Documentation Updates (Parallel Subagents)
+
+**Launch documentation update subagents IN PARALLEL based on Phase 1 results.**
+
+Only launch agents for docs that need updating (from Phase 1 analysis).
+
+**Agent A - README (unless --no-readme):**
+
+```
+Run /prime first.
+Review the changes and determine if README.md needs updating.
+Update if: new packages added, commands changed, architecture shifted, project structure modified.
+Make minimal, focused updates only for what changed.
+```
+
+**Agent B - Root CLAUDE.md and AGENTS.md (unless --no-claude-md):**
+
+```
+Run /prime first.
+Run /claude-md optimize to update the root CLAUDE.md and /agents-md optimize to update the root AGENTS.md.
+Focus on reflecting any new apps, packages, key files, or command changes.
+```
+
+**Agent C - Package CLAUDE.md and AGENTS.md files (unless --no-claude-md):**
+
+```
+Run /prime first.
+For each affected CLAUDE.md and AGENTS.md identified in Phase 1:
+- Navigate to that directory
+- Run /claude-md optimize
+- Run /agents-md optimize
+Only update CLAUDE.md and AGENTS.md files in directories where source code actually changed.
+```
+
+**Agent D - Architecture Docs (unless --no-docs):**
+
+```
+Run /prime first.
+For each architecture doc identified in Phase 1:
+- Read the current doc
+- Update only sections affected by the changes
+- Maintain existing structure and style
+
+Docs to potentially update:
+- docs/architecture/api-catalog.md - API endpoint changes
+- docs/architecture/c4-component.md - Component changes
+- docs/architecture/c4-container.md - Container/service changes
+- docs/architecture/dependencies.md - Dependency changes
+- docs/architecture/decisions/ - New ADRs if major decisions made
+- docs/features/ - Feature changes
+- docs/tech-specs/ - Tech specs changes
+- docs/sdlc/ - SDLC changes
+- docs/runbooks/ - Runbooks changes
+- docs/data/ - Data changes
+```
+
+Wait for all documentation agents to complete.
+
+### Phase 4: Commit & Push (Sequential)
+
+#### Step 4.1: Stage All Changes
+
+```bash
+git add -A
+```
+
+#### Step 4.2: Generate Commit Message
+
+Based on Phase 1 analysis, generate a conventional commit message:
+
+**Type detection:**
+
+- New files in src/, packages/, apps/ → `feat`
+- Modified existing source files → `fix` or `refactor`
+- Only test files → `test`
+- Only docs → `docs`
+- Config files, dependencies → `chore`
+
+**Scope detection:**
+
+- Single package changed → `(package-name)`
+- Multiple packages → `(pkg1,pkg2)` or omit
+- Docs only → `(docs)`
+
+**Format:**
+
+```
+<type>(<scope>): <summary>
+
+<body with bullet points of main changes>
+```
+
+#### Step 4.3: Commit
+
+```bash
+git commit -m "$(cat <<'EOF'
+<generated commit message>
+EOF
+)"
+```
+
+#### Step 4.4: Push (unless --no-push)
+
+```bash
+git push
+```
+
+---
+
+## Completion Report
+
+After all phases complete, provide a summary:
+
+```
+## /ship Complete
+
+### Quality Checks
+- Tests: [PASSED/FIXED/SKIPPED]
+- Lint: [PASSED/FIXED/SKIPPED]
+- Typecheck: [PASSED/FIXED/SKIPPED]
+
+### Documentation Updated
+- README.md: [YES/NO/SKIPPED]
+- CLAUDE.md files: [list or SKIPPED]
+- AGENTS.md: [YES/NO/SKIPPED]
+- Architecture docs: [list or SKIPPED]
+
+### Git
+- Commit: <commit hash>
+- Pushed: [YES/NO]
+```

package/templates/base/.claude/commands/tools.md

@@ -0,0 +1,3 @@
+# List Built-in Tools
+
+List all core, built-in non-mcp development tools available to you. Display in bullet format. Use typescript function syntax with parameters.

package/templates/base/.claude/docs/claude-progress.txt

@@ -0,0 +1,107 @@
+# Hono Boilerplate Progress
+
+## Session 1 - Initializer Agent
+**Date**: 2026-01-02
+**Status**: COMPLETED
+
+---
+
+## Tasks Completed
+
+### 1. Feature List Created ✓
+**File**: `docs/features/feature_list.json`
+
+Created comprehensive test case specification:
+- **Total features**: 261
+- **Functional tests**: 212
+- **Style tests**: 49
+- **Complex journeys (10+ steps)**: 25
+
+Categories covered:
+- Authentication & OAuth flows
+- Multi-tenant account management
+- User CRUD operations
+- Role-based access control (7 roles)
+- Invitation system
+- Session management
+- Audit logging
+- Storage (R2) operations
+- API infrastructure (OpenAPI, rate limiting, CORS)
+- Frontend components (dashboard, sidebar, forms)
+- Accessibility compliance
+- Mobile responsiveness
+- Visual design patterns
+
+### 2. Init Script Created ✓
+**File**: `scripts/init.sh`
+
+Development environment setup script featuring:
+- Node.js 18+ version check
+- Automatic pnpm installation
+- Dependency installation via `pnpm install`
+- `.env` file creation from `.env.example`
+- Cloudflare type generation (`pnpm cf-typegen`)
+- D1 database migrations (`pnpm db:migrate:local`)
+- Optional database seeding
+- Test verification run
+- Command reference summary
+
+### 3. Git Initialized ✓
+**Commit**: `4750dfb`
+**Message**: `CC setup: docs/features/feature_list.json, scripts/init.sh, and project structure`
+
+Files committed:
+- `docs/features/feature_list.json`
+- `scripts/init.sh`
+
+---
+
+## Project State
+
+### Technology Stack
+- **Runtime**: Cloudflare Workers (D1, KV, R2)
+- **Backend**: Hono.js 4.6 + Drizzle ORM + Zod
+- **Frontend**: React 19 + TanStack Router + Tailwind CSS 4.0
+- **Testing**: Vitest (unit) + Playwright (E2E)
+- **Auth**: Google OAuth 2.0 with session-based cookies
+
+### Key Patterns Established
+- Multi-tenant architecture (users → accounts → roles)
+- 7-tier RBAC: ADMIN, MANAGER, EDITOR, AUTHOR, VIEWER, BILLING, ANALYTICS
+- Audit logging for all state changes
+- Soft deletes with restore capability
+- Transaction IDs for request tracing
+
+---
+
+## For Future Agents
+
+### CRITICAL RULES
+1. Features in `feature_list.json` can ONLY have `passes` changed from `false` to `true`
+2. NEVER remove or edit existing features
+3. NEVER use `--force` on git commands
+4. Always check for existing code before building new features
+
+### Development Commands
+```bash
+pnpm dev                    # Start development
+pnpm test                   # Run unit tests
+pnpm test:e2e               # Run E2E tests
+pnpm lint                   # Code linting
+pnpm build                  # Production build
+```
+
+### Next Steps
+1. Run `scripts/init.sh` to set up development environment
+2. Implement features from `feature_list.json` in priority order
+3. Mark features as passing only after tests verify functionality
+4. Continue multi-session development with proper handoffs
+
+---
+
+## Session Handoff Notes
+- All initialization tasks completed successfully
+- Feature list provides comprehensive test coverage roadmap
+- Init script tested and made executable
+- Git repository clean with initial commit
+- Ready for implementation phase in subsequent sessions