Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
Post-save conventions for Platypus frontend forms — where a save lands the user, and what the submit button is called.
Install Form Conventions
$ npx skills add willdady/platypus --skill form-conventions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install willdady/platypus form-conventions --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/form-conventions .claude/skills/form-conventions && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "form-conventions" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/form-conventions into .claude/skills/form-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-conventions", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/willdady/platypus/tree/main/.agents/skills/form-conventionsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add willdady/platypus --skill form-conventions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install willdady/platypus form-conventions --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/form-conventions .agents/skills/form-conventions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "form-conventions" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/form-conventions into .agents/skills/form-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-conventions", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add willdady/platypus --skill form-conventions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install willdady/platypus form-conventions --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/form-conventions .cursor/skills/form-conventions && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "form-conventions" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/form-conventions into .cursor/skills/form-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-conventions", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/willdady/platypus.git --path .agents/skills/form-conventions--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add willdady/platypus --skill form-conventions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install willdady/platypus form-conventions --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/form-conventions .gemini/skills/form-conventions && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "form-conventions" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/form-conventions into .gemini/skills/form-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-conventions", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install willdady/platypus form-conventionsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add willdady/platypus --skill form-conventions -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/form-conventions .github/skills/form-conventions && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "form-conventions" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/form-conventions into .github/skills/form-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-conventions", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add willdady/platypus --skill form-conventions -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install willdady/platypus form-conventions --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/willdady/platypus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/form-conventions .opencode/skills/form-conventions && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "form-conventions" agent skill from https://github.com/willdady/platypus/tree/main/.agents/skills/form-conventions into .opencode/skills/form-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "form-conventions", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
form-conventions- GitHub stars
- 116
- Token cost
- ~916 tokens
- SKILL.md length
- 437 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Post-save conventions for Platypus frontend forms — where a save lands the user, and what the submit button is called.
- Changing a form in apps/frontend
- SKILL.md covers Where a save lands and What the button says
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Its submit button
What it does
Form Conventions is an agent skill from willdady/platypus. Post-save conventions for Platypus frontend forms — where a save lands the user, and what the submit button is called. Use when adding or changing a form in apps/frontend, its submit button, or what happens after it saves.
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. It works with Model Context Protocol. The repository describes itself as: Self-hosted AI Agents for your whole team — on your infrastructure, your models, around the clock. The licence is MIT.
When your agent uses it
- Changing a form in apps/frontend
- Its submit button
- What happens after it saves
Example prompts
- “/form-conventions”
What it can do on your machine
Read from SKILL.md and the folder at commit 2147848. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Form Conventions loads about 916 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 437 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from willdady/platypus at commit 2147848, republished under its MIT licence (© willdady). 437 words, ~916 tokens.
Download SKILL.mdSave it as
.claude/skills/form-conventions/SKILL.md (or your agent's skills folder).- name
- form-conventions
- description
- Post-save conventions for Platypus frontend forms — where a save lands the user, and what the submit button is called. Use when adding or changing a form in apps/frontend, its submit button, or what happens after it saves.
Frontend Form Conventions
Where a save lands
One rule covers every form: a save returns the user to the entity's home, and only leaves the page when the form has no home to return to. Which of the two applies falls out of the entity's shape in the route tree:
| Shape | The form is… | On save | Examples |
|---|---|---|---|
| Collection member | the entity's page, reached from a list | go to list | Agents, Blueprints, Skills, Triggers, MCP, Providers, Webhooks, Workspace Context |
| Entity sub-page | a settings/ child of a page the entity owns | stay | Boards, Dashboards |
| Singleton | one per Workspace/Org/account, so there is no list | stay | Sandbox, Organization, Workspace |
| Dialog or inline | not a page at all | stay | Members, Invitations, Global Context, everything in Chat |
Read the shape off apps/frontend/app. settings/agents/[agentId] renders
the agent edit form — an agent has no detail page, so leaving the form means
returning to settings/agents. A board does have a page, and its form lives
at boards/[boardId]/settings, so saving keeps you there.
Staying means mutate() (or router.refresh()) plus a toast. Never
router.push to the page you are already on.
Creating always navigates — to the new entity where it has a page of its own, otherwise to the list it now belongs to.
Deleting always navigates away from whatever it destroyed, whatever the shape: to the list for a collection member, to the parent otherwise.
A list is wherever the list actually renders, not a route that looks like one.
Triggers navigate to the Workspace home because that is where the trigger list
lives; there is no triggers/ page.
Show full SKILL.md (178 more words)Show less
What the button says
The label names the outcome, so it follows from the destination:
| Case | Label |
|---|---|
| Create, page-level form | Save |
| Edit that navigates to the list | Update |
| Edit saved in place | Save |
| Adding to a surface you stay on | Add |
Update is reserved for the edit-then-leave case — it is the word for a save
you are about to be carried away from. Add covers the in-place additions:
Add column, Add card, Add widget.
Let the form heading name the entity and keep the button to the bare verb
(Save, not Create board). Prefer the bare verb over Save changes too. A
loading state keeps the same verb as the button it replaces, with the repo's
ASCII ellipsis: Saving... under Save, Updating... under Update.
Unlike the destination rule, this one is ahead of the code. Most forms today
label on {id ? "Update" : "Save"} alone, so a stay-in-place edit can still
read Update (Sandbox, Organization, Workspace, Dashboard settings); #793
brings the existing buttons into line. Write new buttons to the rule above,
and leave the stragglers to that issue.
© willdady, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/form-conventions of willdady/platypus.
Open the folder on GitHubat commit 2147848
Compare with similar skills
Form Conventions next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Form Conventions this skillwilldady/platypus | 116 | — | ~916 | Automated safety check: Pass | MIT | |
| Figma use_figma Plugin API Ruleswarpdotdev/warp | 65k | 4 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| MCP Developmentcoollabsio/coolify | 63k | 1 repos | ~949 | Automated safety check: Pass | MIT | |
| Integrating shadcn/ui Componentsgoogle-labs-code/stitch-skills | 8.4k | 4 repos | ~2.3k | Automated safety check: Notes | Apache-2.0 | |
| Figma Design to Codewarpdotdev/warp | 65k | 4 repos | ~2.9k | Automated safety check: Pass | AGPL-3.0 | |
| UI UX Pro Maxsaoudi-h/solar-icons | 182 | 18 repos | ~11k | Automated safety check: Notes | Custom licence |
Similar skills
MCP Development
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
- Official
Integrating shadcn/ui Components
google-labs-code/stitch-skills
Guides finding, installing, customizing and wiring up shadcn/ui components in a project, with MCP tools for the component catalog and registries.
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
UI UX Pro Max
saoudi-h/solar-icons
UI/UX design intelligence for web and mobile. An agent skill from saoudi-h/solar-icons.
Preline UI Components via MCP
htmlstreamofficial/preline
Adds Preline UI components and blocks to HTML files by querying the Preline MCP server, with rules for exact slugs and for clarifying vague requests.
More from willdady/platypus
API Conventions
willdady/platypus
Response-body conventions for the Platypus backend API — the error key for failures, the message key for 2xx status messages, and when to throw a typed error instead of returning a response.
Platypus Tools
willdady/platypus
Platypus tools and tool sets — writing a tool, contributing a tool set from a plugin, scoping tools to a workspace, sharing a tool across sets, chat icons, and custom tool UI.
Add API Endpoint
willdady/platypus
Guide for adding new API endpoints to the Platypus backend using Hono.js — routing, tenant scoping middleware, validation, and database access.
Database Schema Changes
willdady/platypus
Guide for making database schema changes in Platypus using Drizzle ORM — editing the schema, pushing to a dev database, and generating the migration that ships.
Docs Audit
willdady/platypus
Audit one section of the docs content against the code, and report what is wrong, stale, fragile, off-voice, or missing.
Pre Release Check
willdady/platypus
The final gate before a release is cut — go green, reconcile the release PR against what actually landed, sweep what CI can't see, check the roadmap and ADR statuses, optionally deep-review, then…
Related
Works with
Categories
Questions about Form Conventions
What does Form Conventions do?
Post-save conventions for Platypus frontend forms — where a save lands the user, and what the submit button is called. Form Conventions is an agent skill from willdady/platypus. Post-save conventions for Platypus frontend forms — where a save lands the user, and what the submit button is called.
When should I use Form Conventions?
Form Conventions fits situations like: changing a form in apps/frontend; its submit button; what happens after it saves.
How do I install Form Conventions in Claude Code?
Run `npx skills add willdady/platypus --skill form-conventions -a claude-code`. Or copy the skill folder (.agents/skills/form-conventions in willdady/platypus) into .claude/skills/form-conventions in your project. Claude Code loads it when a task matches its description.
How do I install Form Conventions in Codex?
Run `npx skills add willdady/platypus --skill form-conventions -a codex`. Or copy the skill folder (.agents/skills/form-conventions in willdady/platypus) into .agents/skills/form-conventions in your project. Codex loads it when a task matches its description.
Can I use Form Conventions in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add willdady/platypus --skill form-conventions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/form-conventions, .gemini/skills/form-conventions, .github/skills/form-conventions and .opencode/skills/form-conventions in your project.
What does Form Conventions need to run?
SKILL.md names no scripts, command-line tools or credentials: Form Conventions is instructions for the agent only.
Does Form Conventions access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Form Conventions safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Form Conventions use?
Form Conventions is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Form Conventions use?
About 916 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Form Conventions?
Skills that share tags, products or a category with Form Conventions: Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), MCP Development (coollabsio/coolify, 63k stars), Integrating shadcn/ui Components (google-labs-code/stitch-skills, 8.4k stars) and Figma Design to Code (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Form Conventions?
willdady (a GitHub user) maintains it in willdady/platypus, which has 116 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 7, 2026.
Source: willdady/platypus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.