Editorial Briefing
openbooklet.com/s/editorial-briefingopenbooklet.com/s/editorial-briefing@1.0.0GET /api/v1/skills/editorial-briefingArt direction for presenting user data as a personal morning briefing. Defines editorial techniques, layout sections, anti-patterns, and tone. Technical infrastructure comes from the UI Skill, not this file.
How to engage with a user reviewing generated UI. Extracts preferences, classifies feedback complexity, and maintains a natural conversational tone.
A proactive bug hunt across the Breadboard codebase. Pick an area, go looking, and produce a concrete artifact (test, lint rule, or codemod) for anything you find.
A system that detects when you're writing code that already exists as a shared utility. Instead of relying on memory or discipline, ESLint rules surface existing helpers in real-time through IDE errors.
A living reference for writing idiomatic TypeScript and Lit in the Breadboard Visual Editor. Covers type safety, import hygiene, component design, and the patterns that distinguish a great frontender from a merely competent one.
Decompose a user objective into a segmented journey. Each segment is a multi-view mini-app. Segments are separated by LLM decision points where the orchestrator decides what comes next.
Audit, diff, and port changes between TypeScript and Python codebases to keep them in sync during the migration.
Art direction for presenting property listings. Defines available widgets, the context-proportional presentation model, and image path conventions. Technical infrastructure and visual anti-patterns come from the UI Skill.
Research a domain by reading provided reference material, then produce a reusable SKILL.md that teaches any agent how to work in that domain.
Generate multi-file React component bundles with design tokens from natural language descriptions.
How to apply user feedback to an existing React component bundle. Defines hard rules, capability classification, and output expectations.
Auto-indexed from breadboard-ai/breadboard
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.