suitereact-code
Skill14 starsChanged 12 days agoBSD-3-ClauseView on GitHub
Implements a SuiteReact workflow plan, records exact file ownership, and runs checks appropriate to UI, SuiteScript, or shared-library changes. Use for planned changes under apps/, sdf/, or suitereact/.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
After every edit, record exact repo-relative paths:
- Very specific: line 33
Run npm run review:app -- <app-name>.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Implement SuiteReact changes
Usage: /suitereact-code <app-name> [--workflow-dir <path>]
Implement autonomously from the workflow plan.md, or create a workflow from the user goal when none exists. Follow .cursor/rules/react-patterns.mdc, .cursor/rules/netsuite-integration.mdc, .cursor/rules/global.mdc, docs/performance.md, and docs/app-quality-checklist.md.
Procedure
- Move the canonical
workflow.jsontocoding. See suitereact-full-cycle for its contract. - Implement the smallest maintainable change. Use typed request/response DTOs and
handleRestletActionfor environment-transparent app actions. - For SuiteQL, verify field names and syntax with the available NetSuite schema/query tools and execute read-only queries when credentials are available.
- After every edit, record exact repo-relative paths:
npm run workflow -- own <workflow-dir> <file>...Pre-existing dirty files require inspection and explicit --allow-existing. Preserve all unrelated worktree changes.
- Reclassify with
npm run workflow -- classify <workflow-dir>, then run only relevant checks:
| Change | Checks |
| App UI | Prettier, app typecheck, app ESLint |
sdf/ or app SuiteScript | Prettier, root typecheck, exact SDF ESLint |
suitereact/ | Library build plus affected app builds |
- Run
npm run review:app -- <app-name>. Resolve errors and assess warnings; do not mark browser or live checks passed here. - Record checks through
npm run workflow -- check .... On failure, move toblockedwith the exact command and error.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/global.mdcCursor rule
- .cursor/rules/netsuite-integration.mdcCursor rule
- .cursor/rules/react-patterns.mdcCursor rule
- doc-spaces-authorSkill
- doc-spaces-publishSkill
- doc-spaces-searchSkill
- suiteql-cookbookSkill
- suitereact-analyzeSkill
- suitereact-commitSkill
- suitereact-deploySkill
- suitereact-devSkill
- suitereact-full-cycleSkill
- suitereact-reviewSkill
- suitereact-scaffoldSkill
- suitereact-test-actionSkill
- suitereact-testSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.