Dokan Frontend Dev
getdokan/dokan
Add or modify Dokan frontend code (React, TypeScript, Vue, Tailwind).
“Use when implementing or refactoring React/TypeScript components and the task requires decisions about component ownership, feature boundaries, state, data flow, effects, or…”
Install Dify Component Writing Guide
$ npx skills add langgenius/dify --skill how-to-write-component -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install langgenius/dify how-to-write-component --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/how-to-write-component .claude/skills/how-to-write-component && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "how-to-write-component" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/how-to-write-component into .claude/skills/how-to-write-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how-to-write-component", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/langgenius/dify/tree/main/.agents/skills/how-to-write-componentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add langgenius/dify --skill how-to-write-component -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install langgenius/dify how-to-write-component --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/how-to-write-component .agents/skills/how-to-write-component && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "how-to-write-component" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/how-to-write-component into .agents/skills/how-to-write-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how-to-write-component", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langgenius/dify --skill how-to-write-component -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install langgenius/dify how-to-write-component --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/how-to-write-component .cursor/skills/how-to-write-component && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "how-to-write-component" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/how-to-write-component into .cursor/skills/how-to-write-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how-to-write-component", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/langgenius/dify.git --path .agents/skills/how-to-write-component--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add langgenius/dify --skill how-to-write-component -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install langgenius/dify how-to-write-component --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/how-to-write-component .gemini/skills/how-to-write-component && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "how-to-write-component" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/how-to-write-component into .gemini/skills/how-to-write-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how-to-write-component", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install langgenius/dify how-to-write-componentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add langgenius/dify --skill how-to-write-component -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/how-to-write-component .github/skills/how-to-write-component && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "how-to-write-component" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/how-to-write-component into .github/skills/how-to-write-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how-to-write-component", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add langgenius/dify --skill how-to-write-component -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install langgenius/dify how-to-write-component --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/langgenius/dify.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/how-to-write-component .opencode/skills/how-to-write-component && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "how-to-write-component" agent skill from https://github.com/langgenius/dify/tree/main/.agents/skills/how-to-write-component into .opencode/skills/how-to-write-component/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "how-to-write-component", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
how-to-write-component- GitHub stars
- 158k
- Token cost
- ~626 tokens
- SKILL.md length
- 238 words
- Files
- 6 (incl. references)
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
- SKILL.md covers Topic Routing, Scope And Verification and Tailwind CSS
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
About this skill
“Use when implementing or refactoring React/TypeScript components and the task requires decisions about component ownership, feature boundaries, state, data flow, effects, or interaction ownership. Do not use for review-only requests, test-only work, copy-only edits, or styling-only changes.”
Dify Component Writing Guide is a skill in langgenius/dify (158k stars). Its SKILL.md is about 626 tokens, with 5 other files in the folder (references). Licence: Custom licence.
What it can do on your machine
Read from SKILL.md and the folder at commit cecdb28. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dify Component Writing Guide loads about 626 tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 79 tokens; SKILL.md has 238 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 238 words (~626 tokens).
“Use this skill to route component architecture decisions to its bundled references. Read only the references required by the current change.”
- name
- how-to-write-component
Files
SKILL.md and 5 other files (references) in .agents/skills/how-to-write-component of langgenius/dify.
- SKILL.md
- references/data.md
- references/interactions.md
- references/ownership.md
- references/runtime.md
- references/state.md
Open the folder on GitHubat commit cecdb28
Compare with similar skills
Dify Component Writing Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dify Component Writing Guide this skilllanggenius/dify | 158k | — | ~626 | Automated safety check: Pass | Custom licence | |
| Dokan Frontend Devgetdokan/dokan | 288 | — | ~1.9k | Automated safety check: Pass | None | |
| React Idiomsirahardianto/awesome-agv | 157 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Frontend Developmentavibebuilder/claude-prime | 120 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Frontend Typescript Rulesshinpr/ai-coding-project-boilerplate | 232 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Typescript Rulesshinpr/claude-code-workflows | 691 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
React Idioms
irahardianto/awesome-agv
React 19+ patterns: custom hooks, Suspense boundaries, state management, component composition, and web performance.
Frontend Development
avibebuilder/claude-prime
A skill your agent uses for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer.
Frontend Typescript Rules
shinpr/ai-coding-project-boilerplate
Applies React/TypeScript type safety, component design, and state management rules.
Typescript Rules
shinpr/claude-code-workflows
React/TypeScript frontend development rules including type safety, component design, state management, and error handling.
React Code Review
giuseppe-trisciuoglio/developer-kit
Provides comprehensive code review capability for React applications, validates component architecture, hooks usage, React 19 patterns, state management, performance optimization, accessibility…
More from langgenius/dify
Backend Code Review
langgenius/dify
Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.
Cucumber and Playwright E2E Tests
langgenius/dify
Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.
Frontend Code Review
langgenius/dify
Reviews frontend changes under `web/` or `packages/dify-ui/` for concrete defects and broken project contracts, using routed rule packs and a severity scale for findings.
Dify Command Line with difyctl
langgenius/dify
Base skill for the difyctl CLI: discover a Dify server's operations through help output and run them as commands, always with JSON output.
Dify Frontend Testing
langgenius/dify
Use when writing or changing Vitest or React Testing Library tests under `web/` or `packages/dify-ui/`, or when the user explicitly requests frontend test…
Related
Works with
Categories
Questions about Dify Component Writing Guide
How do I install Dify Component Writing Guide in Claude Code?
Run `npx skills add langgenius/dify --skill how-to-write-component -a claude-code`. Or copy the skill folder (.agents/skills/how-to-write-component in langgenius/dify) into .claude/skills/how-to-write-component in your project. Claude Code loads it when a task matches its description.
How do I install Dify Component Writing Guide in Codex?
Run `npx skills add langgenius/dify --skill how-to-write-component -a codex`. Or copy the skill folder (.agents/skills/how-to-write-component in langgenius/dify) into .agents/skills/how-to-write-component in your project. Codex loads it when a task matches its description.
Can I use Dify Component Writing Guide in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add langgenius/dify --skill how-to-write-component -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/how-to-write-component, .gemini/skills/how-to-write-component, .github/skills/how-to-write-component and .opencode/skills/how-to-write-component in your project.
What does Dify Component Writing Guide need to run?
SKILL.md names no scripts, command-line tools or credentials: Dify Component Writing Guide is instructions for the agent only.
Does Dify Component Writing Guide access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Dify Component Writing Guide safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dify Component Writing Guide use?
Dify Component Writing Guide has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Dify Component Writing Guide use?
About 626 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.1k tokens, read only when the agent opens those files.
What are the alternatives to Dify Component Writing Guide?
Skills that share tags, products or a category with Dify Component Writing Guide: Dokan Frontend Dev (getdokan/dokan, 288 stars), React Idioms (irahardianto/awesome-agv, 157 stars), Frontend Development (avibebuilder/claude-prime, 120 stars) and Frontend Typescript Rules (shinpr/ai-coding-project-boilerplate, 232 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dify Component Writing Guide?
langgenius (a GitHub organization) maintains it in langgenius/dify, which has 158,055 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 8, 2026.
Source: langgenius/dify on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.