create-command-center 0.0.0-stage → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (59) hide show
  1. package/LICENSE +21 -0
  2. package/LICENSE.agent-skills +21 -0
  3. package/README.md +42 -2
  4. package/RELEASING.md +25 -0
  5. package/UPSTREAM.md +11 -0
  6. package/bin/create-command-center.mjs +34 -0
  7. package/installer/install.mjs +103 -0
  8. package/installer/template/AGENTS.md +9 -0
  9. package/installer/template/README.md +11 -0
  10. package/installer/template/gitignore +4 -0
  11. package/installer/template/repos/index.md +5 -0
  12. package/package.json +16 -4
  13. package/references/accessibility-checklist.md +160 -0
  14. package/references/definition-of-done.md +67 -0
  15. package/references/observability-checklist.md +92 -0
  16. package/references/orchestration-patterns.md +370 -0
  17. package/references/performance-checklist.md +239 -0
  18. package/references/security-checklist.md +250 -0
  19. package/references/testing-patterns.md +236 -0
  20. package/skills/accessibility-engineering/SKILL.md +133 -0
  21. package/skills/accessibility-engineering/scripts/audit-a11y.sh +233 -0
  22. package/skills/api-and-interface-design/SKILL.md +369 -0
  23. package/skills/browser-testing-with-devtools/SKILL.md +319 -0
  24. package/skills/cc/SKILL.md +24 -0
  25. package/skills/cc/assets/config.md +24 -0
  26. package/skills/cc/assets/progress.md +23 -0
  27. package/skills/cc/references/jobs.md +28 -0
  28. package/skills/cc/references/registration.md +39 -0
  29. package/skills/ci-cd-and-automation/SKILL.md +395 -0
  30. package/skills/code-review-and-quality/SKILL.md +402 -0
  31. package/skills/code-simplification/SKILL.md +331 -0
  32. package/skills/constraint-driven-development/SKILL.md +319 -0
  33. package/skills/constraint-driven-development/references/floor-guard.md +182 -0
  34. package/skills/constraint-driven-development/scripts/quality-gate.mjs +45 -0
  35. package/skills/context-engineering/SKILL.md +353 -0
  36. package/skills/debugging-and-error-recovery/SKILL.md +300 -0
  37. package/skills/deprecation-and-migration/SKILL.md +252 -0
  38. package/skills/documentation-and-adrs/SKILL.md +320 -0
  39. package/skills/doubt-driven-development/SKILL.md +245 -0
  40. package/skills/frontend-ui-engineering/SKILL.md +346 -0
  41. package/skills/git-workflow-and-versioning/SKILL.md +355 -0
  42. package/skills/idea-refine/SKILL.md +195 -0
  43. package/skills/idea-refine/examples.md +238 -0
  44. package/skills/idea-refine/frameworks.md +99 -0
  45. package/skills/idea-refine/refinement-criteria.md +113 -0
  46. package/skills/idea-refine/scripts/idea-refine.sh +15 -0
  47. package/skills/incremental-implementation/SKILL.md +249 -0
  48. package/skills/interview-me/SKILL.md +235 -0
  49. package/skills/observability-and-instrumentation/SKILL.md +238 -0
  50. package/skills/performance-optimization/SKILL.md +267 -0
  51. package/skills/performance-optimization/references/optimization-patterns.md +250 -0
  52. package/skills/planning-and-task-breakdown/SKILL.md +259 -0
  53. package/skills/security-and-hardening/SKILL.md +216 -0
  54. package/skills/security-and-hardening/references/hardening-patterns.md +333 -0
  55. package/skills/shipping-and-launch/SKILL.md +336 -0
  56. package/skills/source-driven-development/SKILL.md +217 -0
  57. package/skills/spec-driven-development/SKILL.md +307 -0
  58. package/skills/test-driven-development/SKILL.md +400 -0
  59. package/skills/using-agent-skills/SKILL.md +194 -0
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 rosstheboss94
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2025 Addy Osmani
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md CHANGED
@@ -1,3 +1,43 @@
1
- # Temporary Holding Version
1
+ # Software Factory Command Center
2
2
 
3
- This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
3
+ This is a skills-only home repo. The user-facing `cc` skill is `skills/cc/SKILL.md`. Start your coding agent here and invoke `cc` to initialize repo pointers or coordinate software work using the shared agent skills.
4
+
5
+ The 26 upstream engineering skills and shared references are preserved from the commit recorded in [UPSTREAM.md](UPSTREAM.md). Central project configurations live under `repos/`. Job requests, config snapshots, progress, checks, reviews, and feedback live under `jobs/`. Product source remains in its own checkout.
6
+
7
+ ## Install a home repo
8
+
9
+ The npm package is prepared locally and awaits publication. After release, users can run the following in a new folder with Node.js 22 or newer and Git installed.
10
+
11
+ ```sh
12
+ mkdir my-command-center
13
+ cd my-command-center
14
+ npx create-command-center@latest .
15
+ ```
16
+
17
+ Choose Codex, Claude Code, or both. For a non-interactive install, pass `--agent codex`, `--agent claude`, or `--agent both`. An explicit destination path can replace `.`.
18
+
19
+ The bootstrap copies a versioned home template, canonical skills, shared references, and project-local discovery copies for the selected agents. It initializes Git, ignores `projects/`, and writes `.command-center.json` so the skill can find the home root. The generated home contains the skill workflows and records. The installer source and tests stay in this distribution repository.
20
+
21
+ Open a fresh agent session in the generated home and select the `cc` skill. Ask `cc init https://github.com/owner/project` in chat. The agent clones into `projects/owner/project` and registers the project centrally. GitHub SSH clone URLs, `owner/repo` shorthand, and local paths are also supported.
22
+
23
+ Identical files are preserved on repeat installation and missing files are restored. Changed managed files are reported before writing anything. Configured settings and job records remain in place. Upgrades involving changed templates require review of those conflicts.
24
+
25
+ For local development and tarball installation before npm publication, see [release instructions](RELEASING.md). The existing Codex plugin metadata remains available for plugin-based installations.
26
+
27
+ ## Operations
28
+
29
+ | Request in chat | Result |
30
+ | --- | --- |
31
+ | `cc init [repo-link-or-path]` | Clone a remote project or register a local checkout |
32
+ | `cc repos` | List repo pointers and setup gaps |
33
+ | `cc config <repo> [change]` | Inspect or update central settings |
34
+ | `cc start <repo> <task>` | Spec, plan, build, verify, review, and prepare a PR |
35
+ | `cc status [repo] [job]` | Inspect saved progress and evidence |
36
+ | `cc resume <repo> <job>` | Reconcile and continue an interrupted job |
37
+ | `cc feedback <repo> <job> <text>` | Record an answer and continue |
38
+
39
+ Start authorizes job branch commits, pushes, and PR creation after checks and review. The workflows follow the upstream skills' approval checkpoints and honor approvals already given. Merge and deployment remain human decisions. These operations are performed by the coding agent through skill instructions. Progress and checks must be backed by recorded evidence.
40
+
41
+ No projects are enrolled automatically. Register the projects you want through `cc init`. Skills may include upstream bundled helpers for their specialized tasks, as documented in `UPSTREAM.md`.
42
+
43
+ Original Command Center code is licensed under [MIT](LICENSE). The upstream skills retain their [MIT license notice](LICENSE.agent-skills).
package/RELEASING.md ADDED
@@ -0,0 +1,25 @@
1
+ # Bootstrap release
2
+
3
+ ## Verify locally
4
+
5
+ Run `npm test` using Node.js 22 or newer and Git. The suite packs the package, installs the tarball through npm offline, and checks generated skill references for Codex and Claude layouts. All fixture homes are temporary.
6
+
7
+ Create a distributable tarball with `npm pack`. To install it before publication, use its absolute path.
8
+
9
+ ```sh
10
+ npm exec --yes --package=/absolute/path/create-command-center-0.2.0.tgz -- create-command-center ./my-home --agent both
11
+ ```
12
+
13
+ Open a fresh Codex session and a fresh Claude Code session in the generated home. Confirm that `cc` and the engineering skills are listed. Exercise `cc init <repo-link>`, inspect its central config and ignored checkout, and repeat it to verify preservation. These live-agent discovery and registration checks complement the package tests.
14
+
15
+ ## Prepare publication
16
+
17
+ Review `npm pack --dry-run --json`. The package allowlist includes the installer, clean home templates, the shared skill library, references, upstream license, and provenance. User repo configs, job history, checkouts, and tests are excluded.
18
+
19
+ The proposed npm name is `create-command-center`. Verify availability and npm account ownership before publishing. Original code uses the MIT license in `LICENSE`. The source repository is `https://github.com/rosstheboss94/command-center`. Preserve the upstream MIT notice in `LICENSE.agent-skills` separately.
20
+
21
+ Align package and plugin versions for a release. Refresh the bundled upstream tree and provenance only when intentionally changing its version. Review template changes, since the installer preserves conflicting files on repeat runs.
22
+
23
+ ## Publish
24
+
25
+ Authenticate with the intended npm account, verify its identity and package rights, and obtain release authorization. Then run `npm publish --access public`. After publication, smoke-test `npx create-command-center@<version> <temporary-folder> --agent both` and verify the generated home in fresh agent sessions. The npm package has not been published.
package/UPSTREAM.md ADDED
@@ -0,0 +1,11 @@
1
+ # Upstream skills
2
+
3
+ Source — https://github.com/addyosmani/agent-skills
4
+
5
+ Commit — `8c99fa36d90068c82d547f7c12a9d67a3e95f4ee`
6
+
7
+ The 26 upstream skill folders under `skills/` and shared checklists under `references/` are copied intact from that commit. Their license is `LICENSE.agent-skills`. The `cc` skill is maintained here.
8
+
9
+ Upstream skill folders include three bundled helpers used by their own guidance. These remain part of the upstream skills. Command Center's workflows and saved records are Markdown and require the host agent's existing tools.
10
+
11
+ To update, review a selected upstream commit, replace its skill folders and shared references together, preserve the local `cc` skill, update this provenance and license, and validate references and discovery before using the new version.
@@ -0,0 +1,34 @@
1
+ #!/usr/bin/env node
2
+ import { parseArgs } from 'node:util';
3
+ import { createInterface } from 'node:readline/promises';
4
+ import { installHome } from '../installer/install.mjs';
5
+
6
+ try {
7
+ const { values, positionals } = parseArgs({
8
+ allowPositionals: true,
9
+ options: { agent: { type: 'string' }, help: { type: 'boolean', short: 'h' } },
10
+ });
11
+ if (values.help) {
12
+ console.log('Usage: create-command-center [directory] [--agent codex|claude|both]');
13
+ } else {
14
+ if (positionals.length > 1) throw new Error('Supply one destination directory.');
15
+ let agent = values.agent;
16
+ if (!agent && process.stdin.isTTY && process.stdout.isTTY) {
17
+ const prompt = createInterface({ input: process.stdin, output: process.stdout });
18
+ try {
19
+ agent = (await prompt.question('Configure codex, claude, or both? [both] ')).trim() || 'both';
20
+ } finally {
21
+ prompt.close();
22
+ }
23
+ }
24
+ if (!agent) throw new Error('Non-interactive installation requires --agent codex|claude|both.');
25
+ const result = await installHome(positionals[0] || '.', agent);
26
+ console.log(`Command Center installed in ${result.destination}`);
27
+ console.log(`Configured agents: ${result.agents.join(', ')}`);
28
+ console.log('Open a new agent session in this folder and invoke the cc skill.');
29
+ console.log('Then ask: cc init https://github.com/owner/project');
30
+ }
31
+ } catch (error) {
32
+ console.error(`Command Center: ${error.message}`);
33
+ process.exitCode = 1;
34
+ }
@@ -0,0 +1,103 @@
1
+ import { readFile, readdir, mkdir, lstat, writeFile, rename } from 'node:fs/promises';
2
+ import { dirname, join, resolve, relative } from 'node:path';
3
+ import { fileURLToPath } from 'node:url';
4
+ import { execFileSync } from 'node:child_process';
5
+
6
+ const packageRoot = fileURLToPath(new URL('../', import.meta.url));
7
+ const markerName = '.command-center.json';
8
+
9
+ async function exists(path) {
10
+ try { await lstat(path); return true; }
11
+ catch (error) { if (error.code === 'ENOENT') return false; throw error; }
12
+ }
13
+
14
+ async function collect(directory, prefix = '') {
15
+ const files = [];
16
+ for (const entry of await readdir(directory, { withFileTypes: true })) {
17
+ const path = join(directory, entry.name);
18
+ const name = join(prefix, entry.name);
19
+ if (entry.isDirectory()) files.push(...await collect(path, name));
20
+ else if (entry.isFile()) files.push([name, await readFile(path)]);
21
+ else throw new Error(`Unexpected template link: ${path}`);
22
+ }
23
+ return files;
24
+ }
25
+
26
+ async function checkParents(destination, path) {
27
+ let current = dirname(path);
28
+ while (current !== destination) {
29
+ if (await exists(current)) {
30
+ const info = await lstat(current);
31
+ if (!info.isDirectory() || info.isSymbolicLink()) throw new Error(`Conflicting directory: ${current}`);
32
+ }
33
+ current = dirname(current);
34
+ }
35
+ }
36
+
37
+ export async function installHome(target, selection) {
38
+ if (!['codex', 'claude', 'both'].includes(selection)) throw new Error('Choose --agent codex, claude, or both.');
39
+ try {
40
+ execFileSync('git', ['--version'], { stdio: 'pipe' });
41
+ } catch {
42
+ throw new Error('Git must be installed and available on PATH.');
43
+ }
44
+ const destination = resolve(target);
45
+ if (await exists(destination)) {
46
+ const info = await lstat(destination);
47
+ if (!info.isDirectory() || info.isSymbolicLink()) throw new Error('Destination must be a real directory.');
48
+ }
49
+ const metadata = JSON.parse(await readFile(join(packageRoot, 'package.json'), 'utf8'));
50
+ const markerPath = join(destination, markerName);
51
+ let previous;
52
+ if (await exists(markerPath)) {
53
+ const info = await lstat(markerPath);
54
+ if (!info.isFile() || info.isSymbolicLink()) throw new Error('Conflicting home marker.');
55
+ previous = JSON.parse(await readFile(markerPath, 'utf8'));
56
+ if (previous.templateVersion !== metadata.version || previous.kind !== 'command-center-home' ||
57
+ !Array.isArray(previous.agents) || previous.agents.some(agent => !['codex', 'claude'].includes(agent))) {
58
+ throw new Error('Existing home marker differs from this release. Preserve it and review an upgrade separately.');
59
+ }
60
+ }
61
+ const chosen = selection === 'both' ? ['codex', 'claude'] : [selection];
62
+ const agents = [...new Set([...(previous?.agents || []), ...chosen])].sort();
63
+ const files = new Map(await collect(join(packageRoot, 'installer/template')));
64
+ files.set('.gitignore', files.get('gitignore'));
65
+ files.delete('gitignore');
66
+ const skills = await collect(join(packageRoot, 'skills'));
67
+ const references = await collect(join(packageRoot, 'references'));
68
+ for (const [name, contents] of skills) files.set(join('skills', name), contents);
69
+ for (const [name, contents] of references) files.set(join('references', name), contents);
70
+ for (const name of ['LICENSE', 'LICENSE.agent-skills', 'UPSTREAM.md']) files.set(name, await readFile(join(packageRoot, name)));
71
+ for (const agent of agents) {
72
+ const folder = agent === 'codex' ? '.agents' : '.claude';
73
+ for (const [name, contents] of skills) files.set(join(folder, 'skills', name), contents);
74
+ for (const [name, contents] of references) files.set(join(folder, 'references', name), contents);
75
+ }
76
+ if (agents.includes('claude')) files.set('CLAUDE.md', Buffer.from('Read AGENTS.md for this home repo’s instructions.\n'));
77
+
78
+ const pending = [];
79
+ const conflicts = [];
80
+ for (const [name, contents] of files) {
81
+ const path = join(destination, name);
82
+ await checkParents(destination, path);
83
+ if (await exists(path)) {
84
+ const info = await lstat(path);
85
+ if (!info.isFile() || info.isSymbolicLink() || !(await readFile(path)).equals(contents)) conflicts.push(name);
86
+ } else pending.push([path, contents]);
87
+ }
88
+ if (conflicts.length) throw new Error(`Existing files differ. No files changed:\n${conflicts.join('\n')}`);
89
+ // Preflight completes before creating the destination or changing managed files.
90
+ await mkdir(destination, { recursive: true });
91
+ for (const [path, contents] of pending) {
92
+ await mkdir(dirname(path), { recursive: true });
93
+ await writeFile(path, contents, { flag: 'wx' });
94
+ }
95
+ if (!(await exists(join(destination, '.git')))) {
96
+ execFileSync('git', ['init', destination], { stdio: 'pipe' });
97
+ }
98
+ const marker = JSON.stringify({ kind: 'command-center-home', templateVersion: metadata.version, agents }, null, 2) + '\n';
99
+ const temporary = join(destination, `${markerName}.${process.pid}.tmp`);
100
+ await writeFile(temporary, marker, { flag: 'wx' });
101
+ await rename(temporary, markerPath);
102
+ return { destination, agents, written: pending.map(([path]) => relative(destination, path)) };
103
+ }
@@ -0,0 +1,9 @@
1
+ # Command Center
2
+
3
+ This folder is the software factory home repo. Its `.command-center.json` marker identifies the home root. Use the `cc` skill to register repositories and run engineering jobs.
4
+
5
+ Shared skills live in `skills/` and their checklists in `references/`. Discoverable copies for the selected agents are installed in their project-local skill directories. Load guidance on demand.
6
+
7
+ See [registered repositories](repos/index.md). Central configuration lives under `repos/`, saved job records under `jobs/`, and cloned projects under the gitignored `projects/`. Resolve checkout paths relative to this home. Read each target project's instructions before working in it.
8
+
9
+ Save exact requests, configuration snapshots, progress, and evidence in the home job records so another session can resume. Product changes belong in the target project's own Git history.
@@ -0,0 +1,11 @@
1
+ # Command Center
2
+
3
+ Open Codex or Claude Code in this folder and select the `cc` skill. Then request `cc init https://github.com/owner/project` in chat. The agent clones it into `projects/owner/project` and saves central settings under `repos/`.
4
+
5
+ Use `cc repos`, `cc config <repo>`, `cc start <repo> <task>`, `cc status`, `cc resume <repo> <job>`, and `cc feedback <repo> <job> <text>` in chat. See `skills/cc/SKILL.md` for the workflow.
6
+
7
+ Starting a job authorizes job-branch commits, pushes, and a ready PR after checks and review. Skills honor existing approvals and require evidence for completion. Merge and deployment remain human decisions.
8
+
9
+ Shared skills come from the commit in `UPSTREAM.md`, with licensing in `LICENSE.agent-skills`. Central configuration and job records are versionable. Project checkouts have their own history.
10
+
11
+ The agent discovery copies are generated from the canonical `skills/` and `references/` trees. Keep these copies synchronized when editing skills. The bootstrap preserves differing files and reports conflicts on repeat installation.
@@ -0,0 +1,4 @@
1
+ /projects/
2
+ .DS_Store
3
+ Thumbs.db
4
+ *.tmp
@@ -0,0 +1,5 @@
1
+ # Registered repositories
2
+
3
+ No projects registered yet. Ask the agent to run `cc init <repo-link-or-local-path>` to add one.
4
+
5
+ Each stable repo ID links to its central `config.md`. Keep this index and those records in sync.
package/package.json CHANGED
@@ -1,6 +1,18 @@
1
1
  {
2
2
  "name": "create-command-center",
3
- "version": "0.0.0-stage",
4
- "stub": true,
5
- "description": "Temporary package placeholder for staged publishing"
6
- }
3
+ "version": "0.2.0",
4
+ "description": "Create a skills-based software factory home repo for Codex and Claude Code.",
5
+ "author": "rosstheboss94",
6
+ "repository": {
7
+ "type": "git",
8
+ "url": "git+https://github.com/rosstheboss94/command-center.git"
9
+ },
10
+ "homepage": "https://github.com/rosstheboss94/command-center#readme",
11
+ "bugs": { "url": "https://github.com/rosstheboss94/command-center/issues" },
12
+ "type": "module",
13
+ "engines": { "node": ">=22" },
14
+ "bin": { "create-command-center": "bin/create-command-center.mjs" },
15
+ "files": ["bin/", "installer/", "skills/", "references/", "LICENSE", "LICENSE.agent-skills", "UPSTREAM.md", "RELEASING.md"],
16
+ "scripts": { "test": "node --test tests/*.test.mjs" },
17
+ "license": "MIT"
18
+ }
@@ -0,0 +1,160 @@
1
+ # Accessibility Checklist
2
+
3
+ Quick reference for WCAG 2.2 AA conformance. Use `frontend-ui-engineering` while building interfaces and `accessibility-engineering` when auditing and remediating them.
4
+
5
+ ## Table of Contents
6
+
7
+ - [Essential Checks](#essential-checks)
8
+ - [Common HTML Patterns](#common-html-patterns)
9
+ - [Testing Tools](#testing-tools)
10
+ - [Quick Reference: ARIA Live Regions](#quick-reference-aria-live-regions)
11
+ - [Common Anti-Patterns](#common-anti-patterns)
12
+
13
+ ## Essential Checks
14
+
15
+ ### Keyboard Navigation
16
+ - [ ] All interactive elements focusable via Tab key
17
+ - [ ] Focus order follows visual/logical order
18
+ - [ ] Focus is visible (outline/ring on focused elements)
19
+ - [ ] Custom widgets have keyboard support (Enter to activate, Escape to close)
20
+ - [ ] No keyboard traps (user can always Tab away from a component)
21
+ - [ ] Skip-to-content link at top of page - visible (at least) on keyboard focus
22
+ - [ ] Modals trap focus while open, return focus on close
23
+
24
+ ### Screen Readers
25
+ - [ ] All images have `alt` text (or `alt=""` for decorative images)
26
+ - [ ] All form inputs have associated labels (`<label>` or `aria-label`)
27
+ - [ ] Buttons and links have descriptive text (not "Click here")
28
+ - [ ] Icon-only buttons have `aria-label`
29
+ - [ ] Page has one `<h1>` and headings don't skip levels
30
+ - [ ] Dynamic content changes announced (`aria-live` regions)
31
+ - [ ] Tables have `<th>` headers with scope
32
+
33
+ ### Visual
34
+ - [ ] Text contrast ≥ 4.5:1 for normal text or ≥ 3:1 for large text (at least 18pt / 24 CSS px, or 14pt / about 18.67 CSS px when bold). Do not round a failing contrast ratio up to the threshold.
35
+ - [ ] UI components contrast ≥ 3:1 against background
36
+ - [ ] Color is not the only way to convey information
37
+ - [ ] Text resizable to 200% without breaking layout
38
+ - [ ] No content that flashes more than 3 times per second
39
+
40
+ ### Forms
41
+ - [ ] Every input has a visible label
42
+ - [ ] Required fields indicated (not by color alone)
43
+ - [ ] Error messages specific and associated with the field
44
+ - [ ] Error state visible by more than color (icon, text, border)
45
+ - [ ] Form submission errors summarized and focusable
46
+ - [ ] Known fields use autocomplete (for example `type="email" autocomplete="email"`)
47
+
48
+ ### Content
49
+ - [ ] Language declared (`<html lang="en">`)
50
+ - [ ] Page has a descriptive `<title>`
51
+ - [ ] Links distinguish from surrounding text (not by color alone)
52
+ - [ ] Touch targets meet 24x24 CSS px (SC 2.5.8, AA), including its spacing and exception rules; 44x44 CSS px is the enhanced AAA target (SC 2.5.5)
53
+ - [ ] Meaningful empty states (not blank screens)
54
+
55
+ ## Common HTML Patterns
56
+
57
+ ### Buttons vs. Links
58
+
59
+ ```html
60
+ <!-- Use <button> for actions -->
61
+ <button onClick={handleDelete}>Delete Task</button>
62
+
63
+ <!-- Use <a> for navigation -->
64
+ <a href="/tasks/123">View Task</a>
65
+
66
+ <!-- NEVER use div/span as buttons -->
67
+ <div onClick={handleDelete}>Delete</div> <!-- BAD -->
68
+ ```
69
+
70
+ ### Form Labels
71
+
72
+ ```html
73
+ <!-- Explicit label association -->
74
+ <label for="email">Email address</label>
75
+ <input id="email" type="email" required />
76
+
77
+ <!-- Implicit wrapping -->
78
+ <label>
79
+ Email address
80
+ <input type="email" required />
81
+ </label>
82
+
83
+ <!-- Hidden label (visible label preferred) -->
84
+ <input type="search" aria-label="Search tasks" />
85
+ ```
86
+
87
+ ### ARIA Roles
88
+
89
+ ```html
90
+ <!-- Navigation -->
91
+ <nav aria-label="Main navigation">...</nav>
92
+ <nav aria-label="Footer links">...</nav>
93
+
94
+ <!-- Status messages -->
95
+ <div role="status" aria-live="polite">Task saved</div>
96
+
97
+ <!-- Alert messages -->
98
+ <div role="alert">Error: Title is required</div>
99
+
100
+ <!-- Modal dialogs -->
101
+ <dialog aria-modal="true" aria-labelledby="dialog-title">
102
+ <h2 id="dialog-title">Confirm Delete</h2>
103
+ ...
104
+ </dialog>
105
+
106
+ <!-- Loading states -->
107
+ <div role="status" aria-busy="true" aria-label="Loading tasks">
108
+ <Spinner />
109
+ </div>
110
+ ```
111
+
112
+ ### Accessible Lists
113
+
114
+ ```html
115
+ <ul role="list" aria-label="Tasks">
116
+ <li>
117
+ <input type="checkbox" id="task-1" aria-label="Complete: Buy groceries" />
118
+ <label for="task-1">Buy groceries</label>
119
+ </li>
120
+ </ul>
121
+ ```
122
+
123
+ ## Testing Tools
124
+
125
+ ```bash
126
+ # Automated audit (versions pinned for repeatable browser-driver behavior)
127
+ npx --yes @axe-core/cli@4.13.0 http://localhost:3000 --exit
128
+ npx --yes pa11y@9.1.1 http://localhost:3000
129
+
130
+ # In browser
131
+ # Chrome DevTools → Lighthouse → Accessibility
132
+ # Chrome DevTools → Elements → Accessibility tree
133
+
134
+ # Screen reader testing
135
+ # macOS: VoiceOver (Cmd + F5)
136
+ # Windows: NVDA (free) or JAWS
137
+ # Linux: Orca
138
+ ```
139
+
140
+ ## Quick Reference: ARIA Live Regions
141
+
142
+ | Value | Behavior | Use For |
143
+ |-------|----------|---------|
144
+ | `aria-live="polite"` | Announced at next pause | Status updates, saved confirmations |
145
+ | `aria-live="assertive"` | Announced immediately | Errors, time-sensitive alerts |
146
+ | `role="status"` | Same as `polite` | Status messages |
147
+ | `role="alert"` | Same as `assertive` | Error messages |
148
+
149
+ ## Common Anti-Patterns
150
+
151
+ | Anti-Pattern | Problem | Fix |
152
+ |---|---|---|
153
+ | `div` as button | Not focusable, no keyboard support | Use `<button>` |
154
+ | Missing `alt` text | Images invisible to screen readers | Add descriptive `alt` |
155
+ | Color-only states | Invisible to color-blind users | Add icons, text, or patterns |
156
+ | Autoplaying media | Disorienting, can't be stopped | Add controls, don't autoplay |
157
+ | Custom dropdown with no ARIA | Unusable by keyboard/screen reader | Use native `<select>` or proper ARIA listbox |
158
+ | Removing focus outlines | Users can't see where they are | Style outlines, don't remove them |
159
+ | Empty links/buttons | "Link" announced with no description | Add text or `aria-label` |
160
+ | `tabindex > 0` | Breaks natural tab order | Use `tabindex="0"` or `-1` only |
@@ -0,0 +1,67 @@
1
+ # Definition of Done
2
+
3
+ A standing, project-wide bar that every change must clear before it counts as done. Unlike acceptance criteria, which vary per task and answer "did we build the right thing?", the Definition of Done is the same every time and answers "is this finished to our standard?". Use it as the final gate in `planning-and-task-breakdown`, `incremental-implementation`, and `shipping-and-launch`.
4
+
5
+ ## Definition of Done vs. Acceptance Criteria
6
+
7
+ | | Acceptance Criteria | Definition of Done |
8
+ |---|---|---|
9
+ | Scope | Specific to one task or spec | Applies to every increment |
10
+ | Changes | Different for each item | Fixed and reused |
11
+ | Answers | "Did we build *this thing*?" | "Is it *ready*?" |
12
+ | Owner | Defined when planning the task | Defined once for the project |
13
+ | Example | "User can reset password via email link" | "Tests pass, no regressions, docs updated" |
14
+
15
+ The two are complementary. A task is done only when **its** acceptance criteria are met **and** the standing Definition of Done is satisfied. Skipping either leaves work that looks finished but is not.
16
+
17
+ ## The Standing Checklist
18
+
19
+ Apply this to every change before declaring it done.
20
+
21
+ ### Correctness
22
+ - [ ] All acceptance criteria for the task are met
23
+ - [ ] Code runs and behaves as intended, verified at runtime, not just compiled or typechecked
24
+ - [ ] New behavior is covered by tests that fail without the change and pass with it
25
+ - [ ] Existing tests still pass; no regressions introduced
26
+ - [ ] Edge cases and error paths are handled, not just the happy path
27
+
28
+ ### Quality
29
+ - [ ] Code reveals intent through naming and structure; no comments needed to explain *what* it does
30
+ - [ ] No duplicated business logic
31
+ - [ ] No dead code, debug output, or commented-out blocks left behind
32
+ - [ ] Changes are scoped to the task; no unrelated refactors snuck in
33
+ - [ ] Linting and formatting pass
34
+
35
+ The depth behind these items lives in `code-review-and-quality` (the five-axis review) and `code-simplification` (reducing complexity without changing behavior).
36
+
37
+ ### Integration
38
+ - [ ] Change works with the rest of the system, not just in isolation
39
+ - [ ] Database migrations, config changes, and feature flags are accounted for
40
+ - [ ] Backward compatibility considered for any public interface or API change
41
+
42
+ ### Documentation
43
+ - [ ] Public interfaces, APIs, and user-facing behavior are documented
44
+ - [ ] Architectural decisions worth preserving are recorded (see `documentation-and-adrs`)
45
+ - [ ] Documentation describes the current state in timeless language, not the change history
46
+
47
+ ### Ship-readiness
48
+ - [ ] Security implications reviewed for any untrusted input, auth, or data handling (see `security-and-hardening`)
49
+ - [ ] Observability in place for new critical paths (logs, metrics, traces) (see `observability-and-instrumentation`)
50
+ - [ ] Rollback path exists for anything risky (see `shipping-and-launch`)
51
+ - [ ] The human has reviewed and approved before merge or deploy
52
+
53
+ ## How to Apply
54
+
55
+ - **Per task**: confirm the Correctness and Quality sections before checking the task off.
56
+ - **Per feature**: confirm Integration and Documentation before considering the feature complete.
57
+ - **Per release**: the full checklist is the floor; `shipping-and-launch` adds the deploy-specific gates on top.
58
+
59
+ Tailor the list to the project once, then reuse it unchanged. A Definition of Done that is renegotiated every sprint is not a Definition of Done.
60
+
61
+ ## Red Flags
62
+
63
+ - "It's done, I just haven't run it yet": unverified work is not done.
64
+ - "Tests pass" used as a synonym for done while docs, regressions, or runtime verification are skipped.
65
+ - A different bar applied depending on deadline pressure.
66
+ - Acceptance criteria treated as the whole bar, with no standing quality floor.
67
+ - "Done" declared before human review on changes that need it.
@@ -0,0 +1,92 @@
1
+ # Observability Checklist
2
+
3
+ Quick reference for instrumenting production code. Use alongside the `observability-and-instrumentation` skill.
4
+
5
+ ## Table of Contents
6
+
7
+ - [On-Call Questions (Start Here)](#on-call-questions-start-here)
8
+ - [Structured Logging](#structured-logging)
9
+ - [Metrics](#metrics)
10
+ - [Distributed Tracing](#distributed-tracing)
11
+ - [Alerting](#alerting)
12
+ - [Dashboards](#dashboards)
13
+ - [Verify the Telemetry](#verify-the-telemetry)
14
+ - [Pre-Launch Gate](#pre-launch-gate)
15
+
16
+ ## On-Call Questions (Start Here)
17
+
18
+ Telemetry without a question is noise. Before instrumenting anything:
19
+
20
+ - [ ] 2–4 questions an on-call engineer will ask about this feature are written down
21
+ - [ ] Every signal below maps to one of those questions
22
+ - [ ] Each question is matched to the right signal type: metrics say **that** something is wrong, traces say **where**, logs say **why**
23
+
24
+ ## Structured Logging
25
+
26
+ - [ ] Logs are structured (JSON) with stable event names — not free-form strings
27
+ - [ ] Every log line carries a correlation/request ID, generated or accepted at the system boundary
28
+ - [ ] Correlation ID is propagated on every outbound call and async boundary (HTTP headers, queue metadata)
29
+ - [ ] Any log stream written by more than one entry point (scheduler, replay endpoint, manual run) carries an entry-point field, set where the run starts and propagated alongside the correlation ID
30
+ - [ ] Log levels are consistent: `error` = invariant broken, someone may act; `warn` = degraded but handled; `info` = significant business event; `debug` = off in production
31
+ - [ ] No secrets, tokens, passwords, or unredacted PII in any log line (hard rule from `security-and-hardening`)
32
+ - [ ] Fields are allowlisted — no whole request/response bodies, no auth headers
33
+ - [ ] External service calls logged with metadata only: endpoint, status, latency, attempt count, sanitized identifiers
34
+ - [ ] Actual log output spot-checked: structured fields, not `[object Object]`
35
+
36
+ ## Metrics
37
+
38
+ - [ ] **RED** instrumented for every endpoint and every external dependency: Rate, Errors, Duration
39
+ - [ ] **USE** instrumented for every resource (queues, pools, hosts): Utilization, Saturation, Errors
40
+ - [ ] Latency is a histogram; p50/p95/p99 queryable — never an average
41
+ - [ ] All labels come from small, fixed sets (route template, status class, provider name)
42
+ - [ ] No unbounded label values: no user IDs, tenant IDs, emails, raw URLs, request IDs, or error message text
43
+ - [ ] Status codes grouped by class (`5xx`, not `503`)
44
+ - [ ] Queue depth and processing duration tracked for every worker/queue
45
+
46
+ ## Distributed Tracing
47
+
48
+ - [ ] OpenTelemetry (or equivalent) initialized at service startup, before other imports
49
+ - [ ] Auto-instrumentation enabled for HTTP, gRPC, and DB clients
50
+ - [ ] Trace context propagated on every outbound call (W3C `traceparent`/`tracestate`) and extracted from every inbound request
51
+ - [ ] Context survives async boundaries — queue messages carry trace metadata
52
+ - [ ] Manual spans only around meaningful internal units of work, with the attributes on-call will filter by
53
+ - [ ] No secrets or PII as span attributes
54
+ - [ ] Head-based sampling at a low default rate; 100% of errors kept if tail sampling is available
55
+
56
+ ## Alerting
57
+
58
+ - [ ] Every alert is symptom-based (error rate, p99 latency, queue age) — causes (CPU, disk, restarts) go to dashboards, not pagers
59
+ - [ ] Every alert is actionable; "ignore it, it self-heals" alerts are deleted
60
+ - [ ] Every alert links to a runbook — minimum three lines: what it means, first query to run, escalation path
61
+ - [ ] Thresholds and durations justified by an SLO or historical data, not guesses
62
+ - [ ] Two severities only: **page** (user-facing, act now) and **ticket** (degradation, act this week)
63
+ - [ ] Each new alert test-fired once: it reached the right channel and the runbook link works
64
+ - [ ] No alerts that fire daily and get acknowledged without action
65
+
66
+ ## Dashboards
67
+
68
+ - [ ] Service health dashboard exists: error rate, latency p99, traffic, saturation
69
+ - [ ] Dependency health panel shows per-service error rates and latency
70
+ - [ ] Dashboard answers the on-call questions from the top of this checklist — not "everything except the answer"
71
+ - [ ] Default time range is sensible (1h–6h, not 30d)
72
+
73
+ ## Verify the Telemetry
74
+
75
+ Instrumentation is code; it can be wrong:
76
+
77
+ - [ ] Forced an error in staging → found it in the logs by correlation ID
78
+ - [ ] Sent test traffic → metric series appear with expected labels and sane values
79
+ - [ ] Followed one request end-to-end in the tracing UI → no broken spans
80
+ - [ ] An induced failure was diagnosed from telemetry alone, without reading the source
81
+
82
+ ## Pre-Launch Gate
83
+
84
+ Before a feature ships to production, all of the following are true:
85
+
86
+ - [ ] Structured logs flowing to the log aggregator
87
+ - [ ] RED metrics visible in dashboards for every new endpoint and dependency
88
+ - [ ] At least one symptom-based alert configured, with runbook, test-fired
89
+ - [ ] A request can be traced across every service it touches
90
+ - [ ] On-call knows where the runbooks are
91
+
92
+ For launch-day monitoring sequence and rollback triggers, see the `shipping-and-launch` skill.