Menu
Create a new glossary term entry with the correct schema, compact body, and lightly sourced Beans field-guide tone.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create or update a bean entry from handwritten scans while preserving line breaks, handling CompanionComment formatting correctly, maintaining spans, and avoiding low-value boilerplate transcription.
Create a new bean entry with the correct file shape, public identifier, frontmatter, imported images, and Beans-specific markdown conventions.
Close out a Beans work session cleanly by validating work, finishing Beads-managed tasks correctly, landing on main, and pruning closed worktrees.
Capture local dev-server screenshots with Playwright for Beans preview workflows, especially for `/beans/` routes and visual verification of new pages or content edits.
Use when adding, changing, or reorganizing AI guidance in this repository. Prefer Rulesync skills over commands, subagents, or hooks for reusable workflows, and always edit Rulesync sources before generating tool-specific AI config files.
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
| name | term-entry |
| description | Create a new glossary term entry with the correct schema, compact body, and lightly sourced Beans field-guide tone. |
Use this skill when creating a new glossary term entry.
$ bean term-entry "<TOPIC>" "<TERM>"
bean is display text for CLI-style formatting. Do not paste this command into the markdown body.
TOPIC and TERM.src/content/terms/.---
name: "<display term>"
summary: "<very short one-line summary>"
aliases:
- "<optional alias>"
---
/beans/terms/.