Guide users to build charts and data visualizations using the Graphic Flutter library. Use when users ask how to create charts, configure chart options, add interactivity, customize appearance, or need help with any aspect of the Graphic charting library.
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.
Search the vault using QMD semantic search. Use PROACTIVELY before reading files directly โ whenever the user asks about past decisions, incidents, people, meetings, architecture, patterns, or any vault content. Always prefer QMD over Grep/Glob for vault queries. Also use after creating/editing notes to check for duplicates and related content.
Use this skill when writing any code that uses LogTape for logging in JavaScript or TypeScript. Covers getting loggers, the structured message syntax, configuration, library author rules, context, lazy evaluation, testing, and common mistakes to avoid. Trigger whenever the user is adding logging to a project, debugging log output, or integrating LogTape with a framework.
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
Adds user-facing change descriptions to DevTools release notes. Use when documenting improvements, fixes, or new features in the NEXT_RELEASE_NOTES.md file.
Bug bounty report writing for H1/Bugcrowd/Intigriti/Immunefi โ report templates, human tone guidelines, impact-first writing, CVSS 3.1 scoring, title formula, impact statement formula, severity decision guide, downgrade counters, pre-submit checklist. Use after validating a finding and before submitting. Never use "could potentially" โ prove it or don't report.
Write and review component documentation (MDX) and registry descriptions. Covers doc structure, description writing, Features, and Composition sections. Use when creating new component docs, updating descriptions, adding Features sections, adding Composition sections, or reviewing component documentation quality.
Specialized guide for creating new Ribir UI widgets. Use this skill when asked to create, implement, or refactor a widget in the Ribir framework, especially when the work should include a gallery showcase or a hands-on UI walkthrough.
Generate markdown documentation for a module or feature
Creates, structures, and reviews technical documentation following the Diรกtaxis framework (tutorials, how-to guides, reference, and explanation pages). Use when a user needs to write or reorganize docs, structure a tutorial vs. a how-to guide, build reference docs or API documentation, create explanation pages, choose between Diรกtaxis documentation types, or improve existing documentation structure. Trigger terms include: documentation structure, Diรกtaxis, tutorials vs how-to guides, organize docs, user guide, reference docs, technical writing.
Update the Sky Map splash screen for a new planetary release. Composites a portrait image onto the base splash with a branded strip. Use when asked to "update splash", "add splash for X release", or "create release branding". ARGUMENTS: "<ReleaseName> <path/to/source.png> [crop x1,y1,x2,y2]"
Review technical exercises and candidate submissions with structured evaluation. Trigger: When reviewing technical exercises, code assessments, candidate submissions, or take-home tests.
Build the Radius CLI (rad) binary from source. Use when compiling rad, cross-compiling for another platform, creating a debug build, or verifying the CLI builds correctly after code changes.
Document application architectures with Mermaid diagrams. Use for: generating architecture overviews, component diagrams, sequence diagrams from code, explaining complex Go codebases, answering architecture questions, suggesting architectural improvements, producing entity-relationship diagrams, and distilling code into human-readable descriptions.
Update, create, review, and find gaps in contributor documentation including CONTRIBUTING.md, docs/contributing/, and docs/architecture/. Use when a task affects contributor setup, build, test, debug, review, or architecture guidance, or when a code review needs a documentation impact assessment.
็ๆ็บฟ็ดข่ฎพ่ฎกๅ่ๅพ๏ผ้ๅ ท/็ฏๅข๏ผใๅฝ็จๆท่ฏด"็ๆ็บฟ็ดขๅพ"ใ"็ป้ๅ ท่ฎพ่ฎก"ใๆณไธบ้่ฆ็ฉๅๆๅบๆฏๅๅปบๅ่ๅพใๆๆ major ็บฟ็ดข็ผบๅฐ clue_sheet ๆถไฝฟ็จใ็กฎไฟ่ทจๅบๆฏ่ง่งไธ่ดใ
ไฝฟ็จ Gemini API ็ๆ JSON ๅงๆฌใ็ฑ create-episode-script subagent ่ฐ็จใ่ฏปๅ step1 ไธญ้ดๆไปถๅ project.json๏ผ่ฐ็จ Gemini ็ๆ็ฌฆๅ Pydantic ๆจกๅ็ JSON ๅงๆฌใ
Use when work in openclaw-channel-dingtalk involves DingTalk real-device validation, PR-scoped testing checklists, ้ช่ฏ TODO drafting, or contributor guidance for this workflow.
