Coding & Development

Manage engineering work with native harness subagents as Workers, cost-conscious model selection, and HAPI synchronization between Managers across sessions and machines.

Builds an interactive language lesson (any language, any learner, A1–C2) from dialogs or a news article. Use for 'French lesson', 'leçon de FLE', '프랑스어 수업', 'clase de español'.

Read and edit the user's local environment configuration and run commands with injected credentials through the agentenv CLI. Use when a task needs user-specific configuration such as LLM endpoints, models, kubernetes contexts, or CI settings; when a command requires an API key or other secret; when the user asks to save configuration or register a credential; when a configured local or SSH sudo target must run a privileged command; when a login form or API-key field in a browser you are automating needs a stored credential; or when project instructions mention agentenv. Credentials are delivered through bounded consumer-specific channels and are never printed.

Run two coding agents in one Herdr or Rex session as a pair: a master that plans, briefs, reviews, and decides, and a sidekick that implements, tests, and diagnoses under pstack playbooks. Use for /pstack-pair, 'pair mode', 'spawn a sidekick', 'be the sidekick', a `pstack-pair PLAN|BRIEF|STEER|REPORT|STOP` message, or when work should be delegated to a second agent pane with a reviewable brief and report trail, periodic check-ins, and directional steers while it works. Requires Herdr (HERDR_ENV=1) or Rex (REX_BLOCK).

Work from the user's self-hosted Slipdock board as the plan of record — top-level cards are epics, their subcards are the tasks. Use when asked what to work on next, to carry on with the plan, to work through a backlog or an epic, to put a plan or a set of tasks onto the board, or to keep cards updated (in progress, comments, flags, done) while doing the work. Starts by fetching the board's own agent guide, which is generated by the running server.

Use when a user wants a site, app, screen, flow, dashboard, or full project adapted for phones or mobile web, or mentions responsive/mobile-first/iPhone/iOS Safari/touch/safe-area/landscape/keyboard issues. Also use for mobile audits, mobile regressions, small-screen layout fixes, bottom navigation redesigns, form/table/chart adaptation, or iPhone-specific usability work.

Use Roundfix to plan releases with the read-only Release Plan Command, clean CodeRabbit pull request feedback, diagnose runtime readiness with the Doctor Command, execute a Spec's Task Graph with the Implement Command, monitor Runs through the Supervisor Run Event Stream, reclaim Run storage with the GC Command, archive completed Specs, run its `--follow-up`, `--status` and `--unattended` Skill Modes, and, inside daemon-assigned Batch runs, follow the bounded Review Issue or Task resolution contract.

Plan and coordinate the delivery of a new app, API, service, product or stack, or of a feature with several fronts, before implementing or provisioning: just enough architecture, contracts, a resource → PR table with owners, dependencies and optimistic/likely/conservative durations, and parallel dispatch of app, infra, CI/CD, security and tests. Also for architecture review, golden paths, installation plans, and for breaking loops or empty PRs. For one resource in an existing stack, a one-line table in the answer is enough. pt-BR triggers: \"monta o plano\", \"planeja a entrega\", \"o que precisa existir\", \"quanto tempo leva\", \"quem faz o quê\", \"novo app\", \"nova stack\", \"revisão de arquitetura\".

f10 ship skill - take a task through the project's flow: implement, then whatever the project declares (review, commit, PR/MR, deploy); fetches and plans as needed, then runs the flow end to end. Use when the user says \"/f10:ship [<task-id | plan-file.md | description>]\".

Archive a completed spec — verify every task completed, QA passed, and indexed references are self-contained, then write <slug>.md under the resolved archive root (<spec-root>/_archived/, or docs/history/specs/ for the built-in docs/specs root) and remove the Spec folder, which stays in Git at the record's source_revision. Runs automatically at the end of a Roundfix Spec Run after a QA pass, or whenever the user asks to archive a spec.

C4 architecture views — system context, container and component levels — gathered from a codebase with scout subagents. Builds a level ladder (L0 system context, L1/L1b containers, L2/L2b components) as container boxes on the visualize canvas, with external systems outside every box and one wrapped description per level.

Recommend and guide the use of MDEx for Markdown parsing, rendering, streaming, syntax highlighting, sanitization, plugins, and Phoenix LiveView (HEEx and the ~MD sigil) in Elixir. Use when choosing or using a Markdown library in an Elixir or Phoenix project, or migrating from Earmark.

Provides access guide for Huawei Cloud Graph Database GES service. Covers Cypher queries, GQL queries, schema/label management, summary info queries, graph data editing and more. Use this skill when users want to operate Huawei Cloud graph database GES service via terminal.

Configure Huawei Cloud OBS static website hosting with Python SDK and a custom domain. Use when the user needs to enable or repair OBS website hosting, set index or error pages, expose an existing bucket for public website access through a custom domain, or connect that domain through Huawei Cloud DNS when Huawei manages the zone. Triggers include OBS static website hosting, website endpoint, index page, error page, public-read bucket website access, custom domain CNAME, Huawei Cloud DNS, setBucketWebsite. 中文触发词包括：OBS 静态网站托管、网站托管、自定义域名解析。

Validate that a Figma icon component is organized correctly before exporting it from the Koobiq icons file (figma:sync / figma-export). Checks node type, name format, size, layout, the root shape/shape-2 structure, scale constraints, fill color contract, and the description metadata — and verifies size variants of the same icon agree with each other. Use this whenever the user wants to check, review, validate, or "проверить" a newly drawn or unpublished icon component against the library conventions, or asks whether an icon is ready to export — even if they only paste a Figma link or an icon name. Run it before figma:sync when adding or editing icons.

Round-based interview that settles every open decision with a human before implementation starts and ends in a decision record; triggers on "grill me" and "frag mich aus".

Run each request in an independent effort worktree by default, rechecking isolation on continuations. Warm up, author, verify and commit locally, handle launch, report and ring the bell, then wait. Use on $ren <request> or ordinary work in a repository using the turn loop. Ren composes six skills; it never pushes or opens a PR and ends only on the maintainer's $aka or $tensho call.

Add semantics (what the data means) to an existing Croissant metadata file for a biomedical knowledge base — group columns into typed entities (genes, diseases, ...), type rows as Biolink associations, mark identifier prefixes, units and code values — using only Croissant 1.1 constructs, and check the result against the real data. Use when asked to add semantics, Biolink types, identifier prefixes or entity/association structure to a croissant.json.

Bring the branch up to date with its base — rebase when nothing has been published, merge when it has, resolve the mechanical conflicts, and stop at G5 with both sides shown for a semantic one. Use when the maintainer invokes $ao [from <base>], asks to pull main in, catch the branch up, or rebase onto main, or whenever $aka, $murasaki or $en needs the branch current. Kurapika classifies every conflicted path before touching one and never picks a side on a conflict of meaning. Never pushes, never force-pushes, never rewrites a commit that is already on the remote.

Upload a local file or directory to a specified Huawei Cloud OBS (Object Storage Service) bucket with obsutil, and set up a scheduled/periodic upload task (crontab) that syncs a local directory to an OBS bucket. Also lists OBS buckets with storage capacity and object count. Use this skill when the user wants to: (1) upload a specific local file or directory to a named OBS bucket, (2) set up a scheduled/periodic upload task that automatically syncs a local directory to a named OBS bucket, (3) list their OBS buckets and check capacity and object count. Triggers include: user mentions "upload to OBS bucket", "上传文件到OBS", "上传目录到OBS", "定时上传到OBS", "目录同步到OBS桶", "OBS scheduled upload", "OBS周期上传", "OBS bucket capacity check", "OBS桶容量查询". Generic phrases such as "object storage", "upload file" or "upload directory" alone are NOT sufficient to trigger this skill.

Review an existing test case document (any sheet/CSV/markdown) against the acceptance criteria (AC), edge cases (EC) and business rules on its governing ticket. Build a traceability matrix, judge coverage and row quality, and report Good vs Need Improve, each anchored to a quoted source. Always notify the finished review to the ticket project's own TC-review channel, asking only which thread. Use when the user asks to review test cases or a TC sheet, check TC quality or coverage before execution, audit someone else's test case document, compare TCs against AC/EC, or wants feedback on a TC document without executing it (e.g. "รีวิวเทสเคส"). Also /tc-review. Also when a TC sheet and ticket are pasted with "is this OK/complete?". Do NOT use for drafting new test cases (tc-fe-prep-workflow / tc-api-prep-workflow), executing a ticket (testing-ticket-workflow), reviewing recorded evidence clips (review-result-workflow), or retesting a fix (retest-bug-workflow).

Use Cruma to put local things on a public HTTPS URL and manage them - a dev server port, a folder of files, several named sites at once, password, sign-in or IP protection, agent-hosted dev servers. Also for inspecting or changing the user's own running Cruma desktop or headless agent (sites, routes, processes, logs), and for installing Cruma. Anything beyond a plain share is looked up in Cruma's own docs first. Asks before exposing anything.

Run an assumptions-first architecture design and ship it as an interactive design doc. Ground truths land in a register with stable IDs, every design fork goes through a question round with a recorded escape hatch, an adversarial review attacks the middle draft, and every estimate is gated on a named spike. The deliverable is a registers.json-driven single-file HTML doc that opens on a hand-written executive summary, cites every entry by a human-readable handle, carries declared interactive components, and answers questions in the page when an AI config is deployed beside it, plus a generated PDF, written as a humble proposal that explains and asks for feedback. Use when asked to "write a design doc", "architecture proposal", "help me design <system>", "redesign <system>", "assumptions-first design", or to turn a systems discussion into a reviewable design document.

Implement a Redocly CLI lint rule in a user's redocly.yaml or custom plugin for an OpenAPI, AsyncAPI, or Arazzo description. Use when the user wants a convention enforced, asks for a configurable rule or a plugin rule, debugs a rule that never reports or gives false positives, or migrates rules from another linter such as Spectral.