UI
DevelopmentuiUI is an Agent Skill for development published in the InsForge/InsForge repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use this skill when contributing to InsForge's reusable UI package. This is for maintainers editing design-system primitives, exports, styles, and package-level component behavior in the InsForge monorepo.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/InsForge/InsForge/blob/HEAD/.agents/skills/insforge-dev/ui/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ui, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
InsForge Dev UI
Use this skill for packages/ui/ work in the InsForge repository.
Scope
packages/ui/src/components/**packages/ui/src/lib/**packages/ui/src/index.tspackages/ui/src/styles.css
Working Rules
-
Put only reusable primitives here.
- If the component is generic across dashboard features or other InsForge apps, it belongs in
packages/ui/. - If it is tightly coupled to one dashboard workflow but should ship to both OSS and cloud hosts, keep it in
packages/dashboard/. - If it is only for the self-hosting host app, keep it in
frontend/.
- If the component is generic across dashboard features or other InsForge apps, it belongs in
-
Preserve the package's implementation style.
- Use
class-variance-authorityfor variants when appropriate. - Use the shared
cn()helper for class merging. - Follow the existing Radix-wrapper and typed-export patterns.
- Use
-
Keep the public surface in sync.
- Export new public components from
packages/ui/src/index.ts. - Avoid adding internal-only abstractions to the package surface unless they are meant to be consumed.
- Never use the TypeScript
anytype. Keep component props and exported helpers strictly typed.
- Export new public components from
-
Validate downstream impact.
- The shared dashboard package consumes this package directly, so UI changes can break
packages/dashboard/even ifpackages/ui/itself builds cleanly.
- The shared dashboard package consumes this package directly, so UI changes can break
Validation
cd packages/ui && npm run buildcd packages/ui && npm run typecheck
Also validate packages/dashboard/ when the changed component is used in the dashboard, and validate frontend/ if the host app integration or CSS entrypoints changed.