Skip to content

Skills

35 skills. A skill is a reusable procedure the assistant runs on request or when its description matches the situation.

Use when asked what skills or commands exist, for a skill list or one skill’s instructions, for the project’s settings, state or template version, or on a bare /act, /act-config, /act-info or /act-version prompt. Prints the skill table, one skill in full, or a script’s output. Does not run any skill.

Source: .act/skills/act/SKILL.md

Use when asked to check accessibility, whether something is usable with keyboard or screen reader, or against WCAG, for one page or component. Gives a severity-ranked list of findings and fixes the ones you approve. Not for checking a build against its design - use act-design-build.

Source: .act/skills/act-a11y/SKILL.md

Use to start a new project from this one, or to adopt another project’s docs or AI tooling (old or foreign template, own structure). Not for setting up the current folder - use act-setup.

Source: .act/skills/act-adopt/SKILL.md

Use after a feature wave, before a handover, or when docs/project might be stale or contradict the code (architecture, coding rules, testing, features, decisions). Brings outdated entries in line with the actual code. Not for template drift - use act-doctor.

Source: .act/skills/act-audit-docs/SKILL.md

Use when a bug is reported, something is broken, or asked to debug or fix specific behavior. Ends with the fix proven by a test that fails before and passes after. Not for cleanup or refactoring found along the way.

Source: .act/skills/act-bug/SKILL.md

Use when asked to check translations or i18n, whether all languages are complete, or after adding a language or new UI text. Gives a per-language report of missing, unused or mismatched keys and fixes the approved ones.

Source: .act/skills/act-check-translations/SKILL.md

Use right after a task is accepted and its evidence (a test run, an outside call, a commit hash) is in hand, or when asked to close out and commit. Leaves the task archived and journaled, committed by pathspec. Never run by a sub-agent.

Source: .act/skills/act-commit/SKILL.md

Use when the session start says archive compaction is due, or when asked to compact or merge the archive or the journal. Merges old archived entries and journal entries word for word into one file per kind and month with a monthly overview, checks nothing was lost, and commits that run on its own. Never run by a sub-agent.

Source: .act/skills/act-compact/SKILL.md

Use when asked to show or change a setting in docs/ai/config.md (“act-config”, “set feedback to manual”). Answered by a script without the model. Not for the Roles table.

Source: .act/skills/act-config/SKILL.md

Use when dependencies are stale, a security advisory needs checking, or asked to update packages or check dependency age. Updates in traceable steps - patch and minor bundled, one commit per major - with checks green after each.

Source: .act/skills/act-deps/SKILL.md

Use when asked to design a logo, icons, a favicon set, an illustration or a product image that should stay in the project. Delivers hand-written SVG or image-model output, checked and placed in the repo. Not for throwaway drafts - use act-design-ideas.

Source: .act/skills/act-design-assets/SKILL.md

Use when asked to build a component from a screenshot, implement a variant chosen via act-design-ideas, or turn a page design into code. Implements it in the project code and checks it in the browser in up to three rounds. Not for exploring options - use act-design-ideas.

Source: .act/skills/act-design-build/SKILL.md

Use when asked for design ideas, variants for a component or page, or what something could look like, before any code exists. Produces three to four preview images from a description, screenshots or links. Not for building the chosen one - use act-design-build.

Source: .act/skills/act-design-ideas/SKILL.md

Use to check for drift against the template, after an update, or when asked whether local overrides still make sense. Runs the cheap mechanical checks (stale overrides, dead IDs, orphaned bridges); content checks only on request. Not for performing an update - use act-update.

Source: .act/skills/act-doctor/SKILL.md

Use to hand this project’s setup to a new project, or to check what a settings export would reveal before sending it anywhere. Writes the project’s own rule deviations, optionally scripts, checklists, agents, skills and topics, to a portable settings file.

Source: .act/skills/act-export-settings/SKILL.md

‘Use when asked to send feedback, “report to the template”, or “feedback: <text>”, or when a rule, workflow, script or skill of the template itself helped, failed or was missing, including a template bug. Sends a pattern about the working method to the template author, never project specifics.’

Source: .act/skills/act-feedback/SKILL.md

Use when the human wants to hand over or leave the session - “hand over”, “can I close the session”, “is it safe to /clear”, “new session”. Checks that nothing is lost, fixes what it can, and ends ready for a bare “continue” in the new session. Never clears on its own.

Source: .act/skills/act-handover/SKILL.md

‘Use when a feature, idea or change request is proposed: “can we add X”, “it would be good if”, “change request”. Checks what exists, offers options with a recommendation, and after the decision files an effort estimate as backlog item and task. Not for planning a decided block - use act-prepare.’

Source: .act/skills/act-idea/SKILL.md

Use when asked which project, folder, branch or template version this session works in, or what is open here (“act-info”). Read-only, no network. Not for the newest version - use act-version.

Source: .act/skills/act-info/SKILL.md

Use when asked what GitHub or GitLab access exists, before act-pr or act-issue when docs/project/integrations.md is missing or older than 30 days, after a token or MCP server changed, or when asked which MCP servers or tools fit the project. Records access read-only; sets up a catalog server only after a yes.

Source: .act/skills/act-integrations/SKILL.md

Use when asked to “show issues”, “show my open stories”, “show issue 42”, to create, comment on or close a GitHub or GitLab issue, or to “start work on issue 42”. Covers issues and stories on the repo host. Not for pull or merge requests - use act-pr.

Source: .act/skills/act-issue/SKILL.md

Use when handed a settings.md or settings.zip file (act-export-settings output) to bring into this project. Mechanical checks sort new, identical and dead items, content overlaps go to a model for judgment, unresolved items land in the inbox. Not for a template update conflict - use act-update.

Source: .act/skills/act-load-settings/SKILL.md

Use when asked to list, look at, fetch, install, update or remove a package (a bundle of rules, skills, roles and checks from outside the template), on “/act-packages”, or after act-update when an installed package has a newer version. Shows the plan and diff first and waits for your yes.

Source: .act/skills/act-packages/SKILL.md

Use when something is reported as slow or asked to speed up a named page, query or endpoint. Ends with that one part measurably faster, shown by numbers from before and after a single change. Not for behavior-preserving restructuring - use act-refactor.

Source: .act/skills/act-perf/SKILL.md

Use when asked to open a pull request, create a merge request, write a PR description, or “send this branch for review” on GitHub or GitLab. Drafts title and description from the branch diff, creates it only after a yes. Not for issues - use act-issue; not for local commits - use act-commit.

Source: .act/skills/act-pr/SKILL.md

Use when planning a larger feature or block, asked to “plan this out”, before work that should run unattended, or when the human says they will be away. Ends with ready, sized tasks and every open question asked in one bundle. Not for a first idea still lacking a decision - use act-idea.

Source: .act/skills/act-prepare/SKILL.md

Use when asked to refactor, clean up or restructure existing code without changing what it does. Works in small steps with tests after each one, after stating goal and scope and checking the test net. Not for making code faster - use act-perf.

Source: .act/skills/act-refactor/SKILL.md

Use when asked to prepare a release, publish a new version, tag a version or generate a changelog. Results in a tagged semantic version with a readable changelog from the commits. Not for ordinary commits - use act-commit.

Source: .act/skills/act-release/SKILL.md

Use when asked to check SEO, why pages are poorly found in search, Lighthouse scores, page speed, or before launching a site. Default is a code check (metadata, headings, links, hreflang, structured data, duplicates, robots.txt, sitemap); on request also a crawl and Lighthouse run against the production build (–live) or the public URL. Fixes only what is approved.

Source: .act/skills/act-seo/SKILL.md

Use when setting up a project in a fresh template clone, or when the owner asks to set up, initialize or install one (triggers “setup”, “initialize”, “install”, “richte … ein”, “neues Projekt”). Docks this checkout onto a project. Not for taking over existing docs - use act-adopt.

Source: .act/skills/act-setup/SKILL.md

Use when asked for a presentation, slides about the project, a talk, or a training deck. Produces the slides as versioned Markdown built from the existing docs and exports them to HTML or PDF.

Source: .act/skills/act-slides/SKILL.md

Use when the human wants to learn a topic, ideally on the project’s code - “teach me …”, “I want to learn …”, “explain … as a lesson”. Writes short Markdown lessons with exercises and a learning record. Not for a single question - answer it in the chat; not for slides - use act-slides.

Source: .act/skills/act-teach/SKILL.md

Use when asked to find test gaps, check test coverage for an area, or backfill tests for existing code. Ends with a risk-ranked list of the real gaps and, after approval, targeted tests rather than coverage percentages.

Source: .act/skills/act-test-gap/SKILL.md

Use to check for or apply a newer template version, or when asked which template version is installed or newest (“update the template”, “act-update”). Brings in the new version only after you have seen the diff and agreed. Not for checking local drift - use act-doctor.

Source: .act/skills/act-update/SKILL.md

Use when asked which template version is installed or which releases the source offers (“act-version”, “is there a newer release”). Writes only the local update note. Not for applying an update - use act-update.

Source: .act/skills/act-version/SKILL.md