Dũng (Wem)
Community@wem2017 · HCM
I'm Huynh Dung, I'm Software Developer from Ho Chi Minh City, VietNam
Agent Skills by Dũng (Wem)
Showing 4 vetted skills indexed across 1 GitHub repositories.
wem2017figma-design
Extract design specs, tokens, and screenshots from Figma frames via MCP or REST API.
wem2017design-handoff
Fetches design sources and maps them to acceptance criteria for implementation and verification.
wem2017git-flow-working
Enforces branch naming, Conventional Commits, PR structure, and rebase-first sync rules for agent-driven Git workflows.
wem2017agentflow-protocol
Defines the GitHub Projects v2 state machine contract coordinating DEV and QC agents.
Frequently Asked Questions About Dũng (Wem)
FAQPage SchemaWhat tasks can I perform using wem2017's AgentFlow skills?▼
You can parse Figma frames to extract specs and tokens, dispatch design sources (repo, artifact, design-system, figma, none) to acceptance criteria, enforce Git branch/commit/PR conventions, and govern work through a 6-column Kanban state machine with DoR/DoD and rework loops.
Who should use these AgentFlow skills?▼
Software developers and DEV/QC agents implementing visual surfaces or verifying implementations against designs. DEV loads design-handoff when building a visual surface; QC loads it when verifying implementation against the design; git-flow-working applies whenever an agent creates branches, commits, or PRs.
How does the Figma design extraction work at runtime?▼
The figma-design skill loads when design.kind is figma in agentflow.yaml. It uses the official Figma MCP server with a PAT/REST fallback, parses the Figma URL and node id, and extracts specs and tokens from a single frame, with revision pinning handled by design-handoff.
What must be read before touching board artifacts or configs?▼
The agentflow-protocol skill must be read first. It defines the core contract: config, plugin constants (6 Status column names, labels, comment and branch prefixes, forbidden paths, rework threshold), the 6-column state machine, DoR/DoD, AGENTFLOW-STATE section, read/write order, and trust rules.
What Git safety rules does git-flow-working enforce?▼
It enforces tech-agnostic conventions: branch naming, Conventional Commits, PR shape, and rebase-first synchronization. Hard safety rules prohibit force-push, merging, and touching forbidden paths whenever an agent creates a branch, commits, or opens/updates a pull request.