js / react / next
General SOP for common requests related to js, react, next.
npx skills add ECNU-ICALK/AutoSkill --skill js-react-next --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# js / react / next General SOP for common requests related to js, react, next. ## Prompt Follow this SOP (replace specifics with placeholders like <PROJECT>/<ENV>/<VERSION>): 1) 父组件的代码 2) jsx 3) import React from 'react 4) import ChildComponent from './ChildComponent 5) const ParentComponent 6) const user 7) name: 'Kuro 8) age: 2 9) breed: 'Norwegian Forest Cat 10) return For each step, include: action, checks, and failure rollback/fallback plan. Output format: for each step number, provide status/result and what to do next. ## Triggers - Use when the user asks for a process or checklist. - Use when you want to reuse a previously mentioned method/SOP. ## Examples ### Example 1 Input: Break this into best-practice, executable steps.
- Prompt
- Triggers
- Examples
- Example 1
What does the js / react / next skill do?
General SOP for common requests related to js, react, next.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill js-react-next --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.