dadafinger
Community@dadafinger
dadafinger provides design-specification review, Figma documentation, and bilingual manual QA skills for Okestro CONTRABASS cloud console planning deliverables.
Agent Skills by dadafinger
Showing 25 vetted skills indexed across 1 GitHub repositories.
manual-image-review
Audits screenshots inside docx manuals via extraction, OCR, and triage-based visual review.
planning-html
Convert product spec markdown into static and interactive HTML mockups using a shared design template.
jp-capture-text-consistency
Validates Japanese UI label consistency between requirement sheets and manual documents.
ia-structure-update
Updates IA menu structure xlsx files with new and changed screens from Figma roadmaps.
figma-spec-review
Reviews Figma spec pages against format, terminology, description, and structure rules.
doc-collect
Collects reference document paths and generates a file index Markdown before planning work.
planning-md
Creates and revises product specification markdown files using a section-contract template.
planning-figma
Creates new three-section Figma frames from product spec HTML or markdown documents.
html-spec-review
Validates consistency between HTML bundle prototypes and markdown planning documents, then applies safe patches.
kr-manual-change-tracker
Registers Korean manual changes into a YAML ledger and validates Screen ID coverage against planning PDFs.
critique-reviewer
Critique design and planning deliverables to produce risk notes and prioritized gap questionnaires.
figma-change-flow
Applies planning and prototype changes to existing Figma nodes through a repeatable workflow.
figma-desc-spec
Writes and reviews Figma spec Description sections following the Okestro CONTRABASS documentation standard.
en-manual-wash
Replaces mistranslated terms in English docx manuals with standard OpenStack terminology.
status-state-change-review
Reviews proposed status value and color changes against OpenStack canonical states.
planning-flow
Orchestrates product planning workflows across Markdown, HTML, and Figma stages with confirmation gates.
openstack-glossary-en
Fills empty English translation columns in multilingual Excel glossary files using OpenStack standard terminology.
kr-manual-quickguide
Inserts internal hyperlinks into Korean CONTRABASS manual quick guide sections.
benchmark-research
Generates benchmarking analysis Markdown documents from local research folder files.
kr-manual-format-review
Inspect and fix formatting consistency in Korean CONTRABASS manual docx files.
jira-validation-triage
Triages Jira validation bug lists into grouped, prioritized spec-revision plans.
okestro-planning-figma
Creates new three-section Figma frames from CONTRABASS planning HTML or spec markdown files.
okestro-planning-html
Renders planning spec markdown into static and interactive standalone HTML prototypes.
okestro-planning-md
Creates and revises CONTRABASS planning spec markdown files using a template-based workflow.
Frequently Asked Questions About dadafinger
FAQPage SchemaWhat tasks can I accomplish with dadafinger's skills?▼
You can review Figma spec nodes for format and terminology compliance, render planning spec markdown into HTML prototypes and Figma frames, track Korean manual changes via YAML ledgers, validate Japanese capture text consistency, triage Jira validation bugs, and wash English manuals to OpenStack standard terminology.
Who are these skills designed for?▼
They target UX planners, technical writers, and QA reviewers working on the Okestro CONTRABASS cloud console. Typical users maintain Korean/English/Japanese manuals, menu IA structure spreadsheets, Figma detail-spec pages, and spec-revision priorities derived from Jira validation bug lists.
How do the planning skills run in practice?▼
The okestro-planning-flow orchestrator chains three independent skills: okestro-planning-md creates or versions spec markdown, okestro-planning-html renders static and interactive HTML from a common template, and okestro-planning-figma generates a new three-part Figma frame. Each step requires user confirmation before proceeding.
What inputs and prerequisites do these skills require?▼
Most skills need source artifacts: docx manuals, xlsx glossary or IA files, Figma node URLs, Jira filter URLs or JQL queries, and research folders with captures. Some skills are read-only (figma-spec-review, html-spec-review stage one) and explicitly forbid write operations; edits go through figma-change-flow.
Do the review skills modify original files?▼
Read-only reviewers like figma-spec-review only report PASS/WARN/FAIL findings. Modifying skills preserve originals: okestro-planning-md clones and version-bumps files, ia-structure-update saves a v_next copy with revision history, and html-spec-review backs up before surgical patching.