cyc-stack 0.9.1 → 0.11.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.
- package/.claude-plugin/plugin.json +1 -1
- package/.codex-plugin/plugin.json +1 -1
- package/.cursor-plugin/plugin.json +1 -1
- package/README.md +3 -2
- package/bin/cyc.mjs +72 -20
- package/docs/README.md +2 -0
- package/docs/context.md +18 -10
- package/docs/project-tools.md +2 -12
- package/docs/runtime.md +5 -1
- package/docs/work-assessments.md +4 -4
- package/docs/work-queue.md +187 -0
- package/methods/cyc-build/SKILL.md +1 -1
- package/methods/cyc-context/SKILL.md +28 -20
- package/methods/cyc-context/references/evidence.md +1 -1
- package/methods/cyc-context/references/templates.md +30 -18
- package/methods/cyc-design/frontend-design/SKILL.md +132 -21
- package/methods/cyc-design/frontend-design/references/color.md +43 -56
- package/methods/cyc-design/frontend-design/references/craft-rules.md +17 -14
- package/methods/cyc-design/frontend-design/references/decision-sheet.md +95 -93
- package/methods/cyc-design/frontend-design/references/experience-review.md +15 -6
- package/methods/cyc-design/frontend-design/references/field-guide.md +439 -0
- package/methods/cyc-design/frontend-design/references/generic-tells.md +83 -32
- package/methods/cyc-design/frontend-design/references/layout-archetypes.md +5 -5
- package/methods/cyc-design/frontend-design/references/patterns.md +108 -0
- package/methods/cyc-design/frontend-design/references/reference-standards.md +118 -22
- package/methods/cyc-design/frontend-design/references/typography.md +59 -44
- package/methods/cyc-design/frontend-design/references/ux-foundations.md +2 -1
- package/methods/cyc-design/frontend-design/references/visual-material.md +43 -8
- package/methods/cyc-design/frontend-design/scripts/contrast.mjs +39 -0
- package/methods/cyc-design/frontend-design/scripts/first-screen.mjs +911 -0
- package/methods/cyc-design/frontend-design/scripts/photo-text.mjs +230 -0
- package/methods/cyc-verify/SKILL.md +1 -1
- package/package.json +6 -1
- package/plugin.json +1 -1
- package/scripts/catalog.mjs +5 -3
- package/scripts/context-review.mjs +364 -261
- package/scripts/hub-page.mjs +275 -0
- package/scripts/hub.mjs +139 -0
- package/scripts/project-tools.mjs +14 -6
- package/scripts/queue-board.mjs +287 -0
- package/scripts/queue.mjs +283 -0
- package/scripts/run-gate.mjs +8 -5
- package/scripts/runtime.mjs +270 -19
- package/scripts/source-snapshot.mjs +20 -2
- package/scripts/work-review.mjs +4 -3
- package/skills/cyc/SKILL.md +12 -4
- package/skills/cyc/references/playbooks/experience.md +2 -0
- package/skills/cyc/references/playbooks/plan.md +2 -0
|
@@ -4,4 +4,6 @@ Use to improve a whole user journey, not one component. Stages: [scout](../../..
|
|
|
4
4
|
|
|
5
5
|
In the scout pass, walk the current journey end to end and find every screen and state it touches. Explore two or three genuinely different approaches, prototyping on the real page when the answer is visual, and recommend one. Build it so the whole journey holds together, not just the changed step. Verify in the real app with the [verify recipe](../../../../methods/cyc-verify/references/recipe.md) (journey, console, layout shift, accessibility) as well as the configured checks.
|
|
6
6
|
|
|
7
|
+
For a homepage redesign, the [frontend method](../../../../methods/cyc-design/frontend-design/SKILL.md) supplies the visual comparison for Explore. Carry the chosen treatment into Build and keep edits within the requested page or journey.
|
|
8
|
+
|
|
7
9
|
**Acceptance:** the full journey works in the real app, the recipe observations are recorded, and every configured check passes. A step that could not be exercised in a real browser is reported as unverified, not passed.
|
|
@@ -6,6 +6,8 @@ Investigate current behavior and run impact analysis before selecting the sequen
|
|
|
6
6
|
|
|
7
7
|
Break the result into reviewable increments, each with an observable outcome, affected areas, prerequisite, verification method, and recovery point. Front-load experiments that could invalidate the design. Separate preparation, implementation, rollout, and external approvals when the project actually requires them. Avoid speculative estimates presented as commitments.
|
|
8
8
|
|
|
9
|
+
When the user wants the plan carried out in order, save its increments as a [work queue](../../../../docs/work-queue.md): one unit per increment, each with an outcome, a playbook, its acceptance criteria, the paths it may change and the units it depends on. State what is true when a unit is done, not how to build it; earlier units change the code later units meet. `queue create` freezes the units, so settle criteria and paths with the user first.
|
|
10
|
+
|
|
9
11
|
Planning does not claim the planned checks have run. When a key assumption remains untested, propose the bounded investigation needed before expensive execution. A planning-only request ends with the plan; it does not authorize building, publishing, or merging it.
|
|
10
12
|
|
|
11
13
|
**Acceptance:** a feasible dependency-aware plan that preserves scope and can be handed to an implementer.
|