clawic/Clawix

macos-ux-trace-harness

Run or change the macOS UX trace harness for action-to-visual-completion latency, scroll stability, fixture pressure, and baseline evidence.

ui-performance-budget

Capture and compare Clawix UI performance budgets for critical flows before optimizing visible or runtime UI behavior.

canonical-catalog-expansion

Add or improve canonical data catalog collections, fields, aliases, relations, evidence tags, docs, and tests.

surface-route-work

Work from a registered surface or transverse route by inspecting nodes, neighbors, edges, contracts, owners, tests, and gaps before editing.

code-hygiene-audit

Audit ClawJS/Clawix code hygiene without editing code, producing categorized findings, baseline status, and validation evidence.

commit-hygiene-public

Apply public, contributor-safe commit hygiene without maintainer-private automation, timestamps, ledger rules, or push policy.

adr-to-guardrail

Turn a new or changed ADR into implemented behavior, routing docs, tests, and guardrails rather than leaving it as standalone prose.

cli-agent-surface-work

Change the public agent-facing CLI surface while preserving registry-backed discovery, JSON envelopes, aliases, docs, and tests.

decision-map-maintenance

Keep decision maps as concise routers from decisions to canonical documents and validation guardrails.

docs-alignment-update

Update docs, playbooks, shims, generated docs, and alignment checks so public instructions route to the right canonical sources.

code-hygiene-cleanup

Execute a bounded ClawJS/Clawix code hygiene cleanup campaign from an audit report, one category and repo at a time.

code-review-risk

Review changes for bugs, regressions, missing tests, safety gaps, public/private leaks, and architecture drift before stylistic comments.

host-dependent-validation

Validate bugs and features that depend on local hosts, localhost, filesystem home state, auth, polling, installed apps, real conversations, or signed native helpers.

performance-investigation

Investigate latency, freezes, memory growth, hitches, dropped frames, or perceived slowness with reproduction and instrumentation before optimizing.

ui-implementation

Implement functional Clawix UI wiring while respecting visual mutation boundaries, pattern contracts, protected surfaces, and debt baselines.

accessibility-governance

Govern Clawix accessibility changes across screen reader behavior, keyboard navigation, focus order, contrast, reduced motion, text scaling, timed interactions, and agent-generated UI.

adoption-canonicity-review

Review or update stable, canonical, any-human, PMF, and adoption claims using adoption/canonicity governance packets.

surface-registry-alignment

Align stable paths, APIs, CLI commands, schemas, events, IDs, storage keys, and UI/programmatic parity with the surface registries.

integration-qa-lab

Build or review an external integration QA lab with official surface snapshots, coverage matrices, fixtures, opt-in live lanes, and safe credential handling.

public-hygiene-review

Review public repository changes for secrets, private paths, signing identities, bundle IDs, generated artifacts, local logs, and private workflow leaks.

compatibility-evolution-work

Add or change stable public state, contracts, routes, migrations, adapters, rescue behavior, or compatibility-sensitive surfaces through the evolution ledger.

secrets-boundary-review

Review secret handling, brokered execution, redaction, vault boundaries, host approval, and public hygiene.

visual-regression

Run and interpret Clawix UI geometry, screenshot, protected-surface, and debt-baseline checks without authorizing visual repair.

ui-canon-review

Review whether a Clawix UI pattern, visual decision, copy change, or component extraction belongs in canon, debt, exception, or protected-surface scope.

architecture-drift-repair

Repair confirmed architecture drift in small batches while preserving public canon and avoiding broad opportunistic refactors.

brand-guidelines

Given an existing Style, generate a human-readable brand guidelines document covering colors, typography, voice, do/don't, imagery rules, and usage examples. Use when the user asks for a brand book, brand guide, or design system document.

canvas-design

Apply the 90/10 visual-to-text rule when composing a piece on a canvas (poster, card, social post). Use when the deliverable lives on a single fixed surface where each element competes for attention.

constitution-drift-audit

Audit code, docs, tests, and registries against the Constitution, ADRs, and decision map without making broad repairs. Use when checking whether the repository is drifting away from accepted architecture.

data-storage-boundary-review

Review storage placement across framework global data, workspace data, host state, sidecars, caches, vaults, and external sources.

host-boundary-review

Review framework vs host ownership for permissions, approvals, grants, native execution, storage, daemons, and Clawix integration.

naming-surface-audit

Audit and improve stable names, aliases, vocabulary, field casing, routes, ports, packages, and agent-search discoverability.

source-file-boundary-refactor

Split or contain large source files according to the source-file boundary ADR without changing behavior opportunistically.

style-apply

Apply a Style to any artifact in the workspace (presentation, card, poster, social post, web page). Use when the user says "apply style X", "render this with style X", or wants to reuse a saved style on a new piece.

style-extract

Inspect a reference (web URL, image, PDF, screenshot) and propose a candidate Style for the workspace. Use when the user says "save this style", "guarda este estilo", or shares a reference and wants to reapply it later.

template-render

Render a Template + data + Style into a final artifact in one of HTML, PDF, PNG, SVG or PPTX. Use whenever the user asks for a concrete deliverable like "make me a poster", "render a card", "give me a one-pager".

theme-factory

Produce variants of an existing Style by shifting tone (light/dark), density (compact/relaxed), or accent (palette rotation) while preserving the brand identity. Use when the user wants alternate themes derived from one brand.