Skip to content

Add soft jsdoc typing#9

Merged
zazzcode merged 10 commits into
mainfrom
add-soft-jsdoc-typing
Jun 20, 2026
Merged

Add soft jsdoc typing#9
zazzcode merged 10 commits into
mainfrom
add-soft-jsdoc-typing

Conversation

@zazzcode

Copy link
Copy Markdown
Owner

Updated all skill and zazz methodology docs and then added soft typing with JS Doc decorators

Skills (.agents/skills/):
- Sync 14 upstream skills from zazz-skills: architecture-doc-builder,
  conformance, doc-check, gh-stack, pr-review, psql, qa-testing,
  standard-builder, worktree, plus updated feature-doc-builder, pr-builder,
  proposal-builder, spec-builder, zazz-board-api.
- Remove obsolete qa/qa-backend/qa-frontend (upstream consolidated into
  qa-testing) and coordinator/planner (no longer needed).
- Keep worker and database-baseline-refresh as local-only.
- Rewrite scripts/sync-skills-from-zazz-skills.sh to discover upstream
  skills with IGNORE_SKILLS (sqlcmd, jira-api) and LOCAL_ONLY_SKILLS
  (worker, database-baseline-refresh), remove obsolete synced skills,
  and support DRY_RUN=1.

.zazz DOCS_ROOT structure:
- Add .zazz/specifications/, .zazz/architecture/, .zazz/execution/
  (gitignored runtime records) per the upstream document model.
- Add .zazz/docs/ with vendored top-level methodology guides
  (agent-execution-discipline, code-review-graph,
  human-in-loop-pr-review-strategy, using-gh-stack, worktree-setup,
  wt-cheat-sheet); excludes methodology/, standards/, proposals/ subdirs.

Standards (.zazz/standards/):
- Vendor 5 generic methodology standards from zazz-skills: code-structure,
  docs-hygiene, docs-hygiene-reference-structure, spec-hygiene, pr-process.
- Add adapted contextual-split.md describing this repo's 3-tier model
  (repo-specific precedence, generic methodology, placeholder stack) and
  sync discipline.
- Add placeholder stack standards (flagged to be expanded via
  standard-builder): http-layer (Fastify), data-layer (Drizzle/PostgreSQL),
  frontend (React+Mantine).
- Rebuild index.yaml with tiers, applies_to, and purposes.
- Repo-specific system-architecture, data-architecture, testing,
  coding-styles left untouched (take precedence).

Docs: update README.md and AGENTS.md to reflect the new structure,
standards tiers, and skills table (qa-testing replaces qa variants).
Repo-specific first-read orientation for agents working in a zazz-board
feature worktree, adapted from the qb-mono orientation:
- main (read-only) as the integration branch instead of dev
- PostgreSQL 15 via Docker on 5433 instead of MS SQL / sqlcmd
- JS/Fastify/React+Mantine stack with Vitest+PactumJS, ESLint,
  markdownlint-cli2, husky + lint-staged (not uv/just/prek/ruff/mypy)
- .zazz DOCS_ROOT layout with standards/, docs/, deliverables/,
  specifications/, architecture/, execution/
- .agents/skills vendored via sync script with IGNORE_SKILLS and
  LOCAL_ONLY_SKILLS
- standard git worktree model (not a .bare Worktrunk container)

Verified command shapes against actual package.json scripts (root + api
+ client) and the husky pre-commit / lint-staged wiring. Index the doc in
.zazz/docs/README.md as the first-read guide.
…seed

- Repo Layout: describe the .bare worktree container accurately — shared
  bare object store under .bare/ with main/ (read-only integration
  worktree) and sibling feature worktrees all sharing one object store;
  Worktrunk optional. Drop the misleading "not a normal single-checkout"
  framing since main/ is right there as the integration clone.
- Database Safety: reframe for this project's dev stage. The dev DB
  (DATABASE_URL) is disposable and dropping/reseeding it via
  npm run db:reset is a routine, expected operation, not a last resort.
  The safety boundary is which database an action targets (dev vs test
  vs prod), backed by the seed-script env guards. db:push and the
  database-baseline-refresh skill are for preserving data across schema
  changes.
- Soften the db:reset command-shape comment from "destructive" to
  "routine in development" to match.
@zazzcode zazzcode merged commit b74ba0e into main Jun 20, 2026
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.

2 participants