mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-10 12:47:04 +00:00
kevinveenbirkenbachandClaude Opus 5.5
86cefeff26
web-svc-css becomes web-svc-design and owns the configuration that lived in group_vars/all/13_design.yml. Consumers switch their css service key to design, and sys-front-inj-css becomes sys-front-inj-design. javascript stays an independent key; a role's optional design.js.j2 is injected together with the design and CSP-hashed like the functional script. An in-repo OKLCH lookup replaces colorscheme_generator. From design.colors.base alone it derives surfaces, text, borders, the primary and status fills with their on-colors, hover and active states and a dedicated dark palette; a unit test proves WCAG AA, and AAA for body text, across six base colors in both modes. Semantic --design-* tokens replace --color-NN-SS in every role stylesheet. The shared element styles sit in the cascade layer infinito-design, so an app's own design system always wins and takes the palette through a variable mapping in its role stylesheet or through its own theming mechanism. design.logo and design.title resolve globally from web-svc-design or per role from its design entry, and false or 0 disables the replacement. The design_assets action renders the logo lockup per slot as SVG, PNG and ICO, and the legacy title keys move into the design entries. Three roles carry the design end to end. The dashboard takes logo, favicon and title from the generator and replaces the hard-coded port-ui colors. Gitea maps its theme variables onto the tokens and mounts the generated logo and a branded start page. Nextcloud receives primary color, logo, name and slogan through occ theming and ships no stylesheet. make design-sync re-renders the static design files of a deployed app, make design-gallery captures before and after screenshots in light, dark, desktop and mobile, and make design-queue orders the roles that are due for a design pass. The i8-designer skill and docs/agents/action/design.md describe that loop. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2.4 KiB
2.4 KiB
Cheatsheet 📋
Each operator workflow has a skill that routes the agent to its authoritative
procedure and drives it — clarifying open requirements first, then acting
autonomously to completion. Most are i8- skills specific to this repository; a
few (such as triage) are portable skills shared across projects.
How to use 🧭
Invoke a skill with its slash command, for example /i8-develop or /i8-quality,
or name the skill in your message to the agent. Supply the concrete target (role,
scope, requirement file, or run URL) in the same message; the skill fills the rest
from its procedure file. Run make install-skills to (re)install them.
Skills 🗂️
| Situation | Skill |
|---|---|
| Building a new feature, app, or larger change | i8-develop |
| Iterating a web app role in compose mode | i8-iterate-compose |
| Iterating a web app role in swarm mode | i8-iterate-swarm |
| Validating every role across both modes, compose then swarm | i8-iterate-roundtrip |
Iterating on svc-runner or the self-hosted runner infrastructure |
i8-iterate-runner |
| Iterating on a GitHub Actions workflow | i8-iterate-workflow |
Writing or updating a Playwright spec for a web-* role |
i8-iterate-playwright |
| Bringing UI roles into the corporate design, role by role from the design queue | i8-designer |
| Running or validating tests for a specific scope | i8-test |
Running the quality gate (make quality) to green |
i8-quality |
Running the full gate (make quality-high: quality plus every lint) to green |
i8-quality-high |
| Cleaning up code, docs, or roles after a change | i8-refactor |
| Checking a branch out into a parallel worktree | i8-worktree-create |
| Releasing a parallel worktree and its slot | i8-worktree-down |
| A GitHub Actions / CI run failed and needs triage | triage |
| A local deploy is failing on the host | i8-debug-local |
Inspecting a *.log or *job-logs.txt file dropped in the workdir |
i8-debug-log |
| Pulling a sibling feature branch and merging it into the current one | i8-merge-sibling |
| Staged changes are ready to be committed | i8-commit |
| A branch is ready to be opened as a pull request | i8-pull-request |
| Pushing a branch through the manual-CI draft → ready-for-review cycle | i8-push-trigger-pull |
| Writing a new requirement | i8-requirement-create |
| Implementing an existing requirement file end to end | i8-requirement-implement |