Trigger when the user wants to learn, implement, debug, or extend "Gooact:160 行 JavaScript 的 React" or a 前端框架 / 库 build-your-own project using JavaScript. Use this skill for staged Claude Code guidance, milestone planning, minimal implementation, and troubleshooting.
Scanned 6/2/2026
Install to Claude Code
npx -y skills add linkxzhou/build-your-own-x-skills --skill frontend-framework-library-react-sweetpalma-gooact-react-in --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Frontend Framework Library React Sweetpalma Gooact React In?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/linkxzhou-frontend-framework-library-react-sweetpalma-gooact)More formats (shields.io, HTML) on the badges page.
---
name: frontend-framework-library-react-sweetpalma-gooact-react-in
description: |
Trigger when the user wants to learn, implement, debug, or extend "Gooact:160 行 JavaScript 的 React" or a 前端框架 / 库 build-your-own project using JavaScript. Use this skill for staged Claude Code guidance, milestone planning, minimal implementation, and troubleshooting.
---
# Gooact:160 行 JavaScript 的 React
Use this skill as a project coach for the original build-your-own tutorial.
## Source
- **Category**: 前端框架 / 库
- **Language / stack**: JavaScript
- **Original resource**: https://medium.com/@sweetpalma/gooact-react-in-160-lines-of-javascript-44e0742ad60f
## Workflow
1. Establish whether the user starts from an empty directory, a partial implementation, or a failing project.
2. Default to `JavaScript` unless the user chooses another stack.
3. Read `references/tutorial-map.md` and convert the source into 4-8 implementation milestones.
4. Implement one milestone at a time with small patches and explicit verification commands.
5. Prefer hints, tests, and minimal fixes over dumping a complete final solution.
6. Preserve the user's existing files and style.
## Milestone template
1. Project skeleton and first runnable command.
2. Core data model and invariants.
3. Input/parser/protocol/UI boundary.
4. Main algorithm or runtime engine.
5. Integration and end-to-end behavior.
6. Diagnostics, tests, and extensions.
## Expected outputs
- A staged implementation plan.
- A minimal project scaffold.
- A focused code patch for the current milestone.
- A debugging explanation and regression test.
No comments yet. Be the first to comment!
Practical guide to testing web applications with screen readers for comprehensive accessibility validation.