Agent Skills: design-interfaces
Design and review interface parameters by semantic role: classify each field by what it IS (data, config, policy, credentials, routing, metadata, protocol context), who owns it, when it changes, and whether a standard name exists, not by the feature it vaguely relates to. Use when designing or reviewing ANY interface shape - API request/response params, wire/protocol fields, config schemas, tool definitions, event payloads, function signatures with option bags. Triggers - designing a new endpoint/wire field/config block, reviewing a PR that adds or changes interface fields, "review the interfaces", any plan-feature/implement-feature step that defines or changes a contract.
ID: agenta-ai/agenta/design-interfaces
4,879724
Install this agent skill to your local
Skill Files
The files that make up design-interfaces.
More agent skills
- write-docsUse when writing or editing documentation pages (concept pages, how-to guides, API reference prose, tutorials) under docs/. Provides the writing style, voice, and structural rules for Agenta docs. Apply this skill before drafting any new docs page, and include it in the brief for any subagent tasked with writing docs.
- update-api-docsUpdate the API reference documentation by downloading the latest OpenAPI spec from production and regenerating the Docusaurus API docs
- create-changelog-announcementUse this skill to create and publish changelog announcements for new features, improvements, or bug fixes. This skill handles the complete workflow - creating detailed changelog documentation pages, regenerating the in-app What's New data, and ensuring everything follows project standards. Use when the user mentions adding changelog entries, documenting new features, creating release notes, or announcing product updates.
- write-pr-descriptionWrite PR titles and descriptions the way a staff engineer would. Use when drafting or editing a pull request title and body, before running `gh pr create`, or any time the user asks for a PR description, summary, or release-notes-style writeup of a change. Apply this skill from the start, not as a cleanup pass after a generic first draft.
- triage-findingsCoordinate findings work with the user, decide whether scan, test, or sync should run, and turn the current findings set into a ready plan. Accept optional `path` and GitHub PR `url`; default to `path=infer`. Confirm effective variables before starting.
- scan-codebasePerform a fresh-context scan of code and docs that turns verification observations and missing-test gaps into findings. Accept optional `path` and `depth` parameters and default to `path=infer`, `depth=deep`. Confirm effective variables before starting.