@bastani/atomic 0.5.11 → 0.5.12-1

package/.agents/skills/bun/SKILL.md

@@ -0,0 +1,199 @@
+---
+name: Bun
+description: Use when building, testing, or deploying JavaScript/TypeScript applications. Reach for Bun when you need to run scripts, install packages, bundle code, or test applications — it's a drop-in replacement for Node.js with integrated package manager, test runner, and bundler.
+metadata:
+    mintlify-proj: bun
+    version: "1.0"
+    internal: true
+---
+
+# Bun Skill Reference
+
+## Product Summary
+
+Bun is an all-in-one JavaScript/TypeScript toolkit that replaces Node.js, npm, and bundlers with a single fast binary. It includes a runtime (powered by JavaScriptCore), package manager, test runner, and bundler. Key files: `bunfig.toml` (configuration), `package.json` (scripts and dependencies), `bun.lock` (lockfile). Primary CLI commands: `bun run`, `bun install`, `bun test`, `bun build`. See https://bun.com/docs for comprehensive documentation.
+
+## When to Use
+
+- **Running scripts**: Execute `.js`, `.ts`, `.jsx`, `.tsx` files directly with `bun run` or `bun <file>` — no compilation step needed
+- **Package management**: Install dependencies with `bun install` (25x faster than npm) or add packages with `bun add`
+- **Testing**: Write and run Jest-compatible tests with `bun test` with TypeScript support built-in
+- **Bundling**: Bundle applications for browsers or servers with `bun build` or `Bun.build()` API
+- **HTTP servers**: Build servers with `Bun.serve()` API with native WebSocket and streaming support
+- **Monorepos**: Manage workspaces with `bun install --filter` and run scripts across packages
+- **Development**: Use watch mode (`--watch`) for live reloading during development
+- **Deployment**: Compile standalone executables with `bun build --compile` or deploy to Vercel, Railway, etc.
+
+## Quick Reference
+
+### Essential Commands
+
+| Task                 | Command                                              |
+| -------------------- | ---------------------------------------------------- |
+| Run a file           | `bun run index.ts` or `bun index.ts`                 |
+| Run a script         | `bun run dev` (from package.json)                    |
+| Install dependencies | `bun install`                                        |
+| Add a package        | `bun add react` or `bun add -d @types/node`          |
+| Remove a package     | `bun remove react`                                   |
+| Run tests            | `bun test`                                           |
+| Watch tests          | `bun test --watch`                                   |
+| Build for browser    | `bun build ./index.tsx --outdir ./dist`              |
+| Build for server     | `bun build ./index.tsx --outdir ./dist --target bun` |
+| Watch build          | `bun build ./index.tsx --outdir ./dist --watch`      |
+| Run with watch mode  | `bun --watch run index.ts`                           |
+| Execute a package    | `bunx cowsay "Hello"`                                |
+
+### Configuration Files
+
+| File            | Purpose                                                       |
+| --------------- | ------------------------------------------------------------- |
+| `bunfig.toml`   | Bun-specific configuration (optional, zero-config by default) |
+| `package.json`  | Project metadata, scripts, dependencies                       |
+| `bun.lock`      | Lockfile (text-based, replaces package-lock.json)             |
+| `tsconfig.json` | TypeScript configuration (Bun respects this)                  |
+
+### Key bunfig.toml Sections
+
+```toml
+[install]
+linker = "hoisted"  # or "isolated" for strict dependency isolation
+dev = true          # install devDependencies
+optional = true     # install optionalDependencies
+peer = true         # install peerDependencies
+
+[test]
+root = "."
+coverage = false
+coverageThreshold = 0.9
+
+[run]
+shell = "system"    # or "bun" for Bun's shell
+bun = true          # alias node to bun in scripts
+```
+
+### File Type Support
+
+Bun natively transpiles and executes:
+- `.js`, `.jsx` — JavaScript and JSX
+- `.ts`, `.tsx` — TypeScript and TSX
+- `.json`, `.jsonc`, `.toml`, `.yaml` — Data files (parsed at build time)
+- `.html` — HTML with asset bundling
+- `.css` — CSS bundling
+
+## Decision Guidance
+
+| Scenario                 | Use                                                     | Why                                                                         |
+| ------------------------ | ------------------------------------------------------- | --------------------------------------------------------------------------- |
+| **Package installation** | `bun install` vs `npm install`                          | Bun is 25x faster, uses global cache, supports workspaces                   |
+| **Linker strategy**      | `--linker isolated` vs `--linker hoisted`               | Isolated prevents phantom dependencies; hoisted is traditional npm behavior |
+| **Build target**         | `--target browser` vs `--target bun` vs `--target node` | Browser for web apps, bun for server code, node for Node.js compatibility   |
+| **Module format**        | `--format esm` vs `--format cjs`                        | ESM is default; use CJS for CommonJS compatibility                          |
+| **Watch mode**           | `--watch` vs manual restart                             | Use `--watch` for development; Bun uses OS-native file watchers (fast)      |
+| **Test execution**       | `--concurrent` vs sequential                            | Concurrent for independent tests; sequential for tests with shared state    |
+| **Bundling**             | `bun build` vs `Bun.build()` API                        | CLI for simple builds; API for programmatic control and in-memory bundling  |
+
+## Workflow
+
+### 1. Initialize a Project
+```bash
+bun init my-app
+cd my-app
+```
+Choose template: Blank, React, or Library. Creates `package.json`, `tsconfig.json`, `bunfig.toml`.
+
+### 2. Install Dependencies
+```bash
+bun install
+# or add specific packages
+bun add react
+bun add -d @types/node typescript
+```
+Generates `bun.lock` lockfile. Use `--frozen-lockfile` in CI for reproducible builds.
+
+### 3. Write Code
+Create `.ts`, `.tsx`, `.js`, or `.jsx` files. Bun transpiles on the fly.
+
+### 4. Run Code
+```bash
+bun run index.ts
+# or with watch mode
+bun --watch run index.ts
+```
+
+### 5. Add Scripts to package.json
+```json
+{
+  "scripts": {
+    "dev": "bun --watch run src/index.ts",
+    "build": "bun build ./src/index.tsx --outdir ./dist",
+    "test": "bun test",
+    "start": "bun run dist/index.js"
+  }
+}
+```
+
+### 6. Run Scripts
+```bash
+bun run dev
+bun run build
+bun run test
+```
+
+### 7. Test
+```bash
+# Write tests in *.test.ts or *.spec.ts
+bun test
+bun test --watch
+bun test --coverage
+```
+
+### 8. Bundle for Production
+```bash
+bun build ./src/index.tsx --outdir ./dist --minify
+# or for a server
+bun build ./src/server.ts --outdir ./dist --target bun --minify
+```
+
+### 9. Deploy
+Commit `bun.lock` to version control. In CI, use `bun ci` (equivalent to `bun install --frozen-lockfile`).
+
+## Common Gotchas
+
+- **Watch mode flag placement**: Use `bun --watch run dev`, not `bun run dev --watch`. Flags after the script name are passed to the script itself.
+- **Lifecycle scripts**: Bun does not execute `postinstall` scripts for security. Add packages to `trustedDependencies` in `package.json` to allow them.
+- **Node.js compatibility**: Bun aims for Node.js compatibility but is not 100% complete. Check `/runtime/nodejs-compat` for current status.
+- **TypeScript errors in Bun global**: Install `@types/bun` and configure `tsconfig.json` with `"lib": ["ESNext"]` and `"module": "Preserve"`.
+- **Module resolution**: Bun supports both ESM and CommonJS. Use `import` for ESM (recommended) or `require()` for CommonJS.
+- **Bundler is not a type checker**: Use `tsc` separately for type checking and `.d.ts` generation; `bun build` only transpiles.
+- **Auto-install disabled in production**: Set `install.auto = "disable"` in `bunfig.toml` for production environments.
+- **Phantom dependencies**: Use `--linker isolated` to prevent accidental imports of transitive dependencies.
+- **Environment variables**: Bun auto-loads `.env`, `.env.local`, `.env.[NODE_ENV]`. Disable with `env = false` in `bunfig.toml`.
+- **Minification by default for bun target**: When `target: "bun"`, identifiers are minified by default; use `minify: false` to disable.
+
+## Verification Checklist
+
+Before submitting work with Bun:
+
+- [ ] Run `bun install` to ensure dependencies are locked
+- [ ] Run `bun test` to verify all tests pass
+- [ ] Run `bun run build` (or your build script) and verify output in `dist/` or configured `outdir`
+- [ ] Test the built output: `bun run dist/index.js` or `node dist/index.js` (if targeting Node.js)
+- [ ] Check `bun.lock` is committed to version control
+- [ ] Verify `bunfig.toml` has correct configuration for your environment (dev vs. production)
+- [ ] Run `bun run --filter <pattern> <script>` in monorepos to test workspace scripts
+- [ ] For HTTP servers, test with `curl` or browser: `curl http://localhost:3000`
+- [ ] For bundled apps, check bundle size: `ls -lh dist/`
+- [ ] Verify no console errors or warnings in test output
+- [ ] If using TypeScript, ensure `tsconfig.json` is properly configured
+
+## Resources
+
+- **Comprehensive navigation**: https://bun.com/docs/llms.txt — Full page-by-page listing for agent navigation
+- **Runtime documentation**: https://bun.com/docs/runtime — Execute files, scripts, and use Bun APIs
+- **Package manager**: https://bun.com/docs/pm/cli/install — Install, add, remove, and manage dependencies
+- **Test runner**: https://bun.com/docs/test — Write and run Jest-compatible tests
+- **Bundler**: https://bun.com/docs/bundler — Bundle for browsers and servers
+
+---
+
+> For additional documentation and navigation, see: https://bun.com/docs/llms.txt

package/.agents/skills/clarify/SKILL.md

@@ -0,0 +1,183 @@
+---
+name: clarify
+description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.
+version: 2.1.1
+user-invocable: true
+argument-hint: "[target]"
+---
+
+Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use.
+
+## MANDATORY PREPARATION
+
+Invoke /impeccable — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /impeccable teach first. Additionally gather: audience technical level and users' mental state in context.
+
+---
+
+## Assess Current Copy
+
+Identify what makes the text unclear or ineffective:
+
+1. **Find clarity problems**:
+   - **Jargon**: Technical terms users won't understand
+   - **Ambiguity**: Multiple interpretations possible
+   - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file"
+   - **Length**: Too wordy or too terse
+   - **Assumptions**: Assuming user knowledge they don't have
+   - **Missing context**: Users don't know what to do or why
+   - **Tone mismatch**: Too formal, too casual, or inappropriate for situation
+
+2. **Understand the context**:
+   - Who's the audience? (Technical? General? First-time users?)
+   - What's the user's mental state? (Stressed during error? Confident during success?)
+   - What's the action? (What do we want users to do?)
+   - What's the constraint? (Character limits? Space limitations?)
+
+**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets.
+
+## Plan Copy Improvements
+
+Create a strategy for clearer communication:
+
+- **Primary message**: What's the ONE thing users need to know?
+- **Action needed**: What should users do next (if anything)?
+- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?)
+- **Constraints**: Length limits, brand voice, localization considerations
+
+**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words.
+
+## Improve Copy Systematically
+
+Refine text across these common areas:
+
+### Error Messages
+**Bad**: "Error 403: Forbidden"
+**Good**: "You don't have permission to view this page. Contact your admin for access."
+
+**Bad**: "Invalid input"
+**Good**: "Email addresses need an @ symbol. Try: name@example.com"
+
+**Principles**:
+- Explain what went wrong in plain language
+- Suggest how to fix it
+- Don't blame the user
+- Include examples when helpful
+- Link to help/support if applicable
+
+### Form Labels & Instructions
+**Bad**: "DOB (MM/DD/YYYY)"
+**Good**: "Date of birth" (with placeholder showing format)
+
+**Bad**: "Enter value here"
+**Good**: "Your email address" or "Company name"
+
+**Principles**:
+- Use clear, specific labels (not generic placeholders)
+- Show format expectations with examples
+- Explain why you're asking (when not obvious)
+- Put instructions before the field, not after
+- Keep required field indicators clear
+
+### Button & CTA Text
+**Bad**: "Click here" | "Submit" | "OK"
+**Good**: "Create account" | "Save changes" | "Got it, thanks"
+
+**Principles**:
+- Describe the action specifically
+- Use active voice (verb + noun)
+- Match user's mental model
+- Be specific ("Save" is better than "OK")
+
+### Help Text & Tooltips
+**Bad**: "This is the username field"
+**Good**: "Choose a username. You can change this later in Settings."
+
+**Principles**:
+- Add value (don't just repeat the label)
+- Answer the implicit question ("What is this?" or "Why do you need this?")
+- Keep it brief but complete
+- Link to detailed docs if needed
+
+### Empty States
+**Bad**: "No items"
+**Good**: "No projects yet. Create your first project to get started."
+
+**Principles**:
+- Explain why it's empty (if not obvious)
+- Show next action clearly
+- Make it welcoming, not dead-end
+
+### Success Messages
+**Bad**: "Success"
+**Good**: "Settings saved! Your changes will take effect immediately."
+
+**Principles**:
+- Confirm what happened
+- Explain what happens next (if relevant)
+- Be brief but complete
+- Match the user's emotional moment (celebrate big wins)
+
+### Loading States
+**Bad**: "Loading..." (for 30+ seconds)
+**Good**: "Analyzing your data... this usually takes 30-60 seconds"
+
+**Principles**:
+- Set expectations (how long?)
+- Explain what's happening (when it's not obvious)
+- Show progress when possible
+- Offer escape hatch if appropriate ("Cancel")
+
+### Confirmation Dialogs
+**Bad**: "Are you sure?"
+**Good**: "Delete 'Project Alpha'? This can't be undone."
+
+**Principles**:
+- State the specific action
+- Explain consequences (especially for destructive actions)
+- Use clear button labels ("Delete project" not "Yes")
+- Don't overuse confirmations (only for risky actions)
+
+### Navigation & Wayfinding
+**Bad**: Generic labels like "Items" | "Things" | "Stuff"
+**Good**: Specific labels like "Your projects" | "Team members" | "Settings"
+
+**Principles**:
+- Be specific and descriptive
+- Use language users understand (not internal jargon)
+- Make hierarchy clear
+- Consider information scent (breadcrumbs, current location)
+
+## Apply Clarity Principles
+
+Every piece of copy should follow these rules:
+
+1. **Be specific**: "Enter email" not "Enter value"
+2. **Be concise**: Cut unnecessary words (but don't sacrifice clarity)
+3. **Be active**: "Save changes" not "Changes will be saved"
+4. **Be human**: "Oops, something went wrong" not "System error encountered"
+5. **Be helpful**: Tell users what to do, not just what happened
+6. **Be consistent**: Use same terms throughout (don't vary for variety)
+
+**NEVER**:
+- Use jargon without explanation
+- Blame users ("You made an error" → "This field is required")
+- Be vague ("Something went wrong" without explanation)
+- Use passive voice unnecessarily
+- Write overly long explanations (be concise)
+- Use humor for errors (be empathetic instead)
+- Assume technical knowledge
+- Vary terminology (pick one term and stick with it)
+- Repeat information (headers restating intros, redundant explanations)
+- Use placeholders as the only labels (they disappear when users type)
+
+## Verify Improvements
+
+Test that copy improvements work:
+
+- **Comprehension**: Can users understand without context?
+- **Actionability**: Do users know what to do next?
+- **Brevity**: Is it as short as possible while remaining clear?
+- **Consistency**: Does it match terminology elsewhere?
+- **Tone**: Is it appropriate for the situation?
+
+Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human.

package/.agents/skills/colorize/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: colorize
+description: Add strategic color to features that are too monochromatic or lack visual interest, making interfaces more engaging and expressive. Use when the user mentions the design looking gray, dull, lacking warmth, needing more color, or wanting a more vibrant or expressive palette.
+version: 2.1.1
+user-invocable: true
+argument-hint: "[target]"
+---
+
+Strategically introduce color to designs that are too monochromatic, gray, or lacking in visual warmth and personality.
+
+## MANDATORY PREPARATION
+
+Invoke /impeccable — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /impeccable teach first. Additionally gather: existing brand colors.
+
+---
+
+## Assess Color Opportunity
+
+Analyze the current state and identify opportunities:
+
+1. **Understand current state**:
+   - **Color absence**: Pure grayscale? Limited neutrals? One timid accent?
+   - **Missed opportunities**: Where could color add meaning, hierarchy, or delight?
+   - **Context**: What's appropriate for this domain and audience?
+   - **Brand**: Are there existing brand colors we should use?
+
+2. **Identify where color adds value**:
+   - **Semantic meaning**: Success (green), error (red), warning (yellow/orange), info (blue)
+   - **Hierarchy**: Drawing attention to important elements
+   - **Categorization**: Different sections, types, or states
+   - **Emotional tone**: Warmth, energy, trust, creativity
+   - **Wayfinding**: Helping users navigate and understand structure
+   - **Delight**: Moments of visual interest and personality
+
+If any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.
+
+**CRITICAL**: More color ≠ better. Strategic color beats rainbow vomit every time. Every color should have a purpose.
+
+## Plan Color Strategy
+
+Create a purposeful color introduction plan:
+
+- **Color palette**: What colors match the brand/context? (Choose 2-4 colors max beyond neutrals)
+- **Dominant color**: Which color owns 60% of colored elements?
+- **Accent colors**: Which colors provide contrast and highlights? (30% and 10%)
+- **Application strategy**: Where does each color appear and why?
+
+**IMPORTANT**: Color should enhance hierarchy and meaning, not create chaos. Less is more when it matters more.
+
+## Introduce Color Strategically
+
+Add color systematically across these dimensions:
+
+### Semantic Color
+- **State indicators**:
+  - Success: Green tones (emerald, forest, mint)
+  - Error: Red/pink tones (rose, crimson, coral)
+  - Warning: Orange/amber tones
+  - Info: Blue tones (sky, ocean, indigo)
+  - Neutral: Gray/slate for inactive states
+
+- **Status badges**: Colored backgrounds or borders for states (active, pending, completed, etc.)
+- **Progress indicators**: Colored bars, rings, or charts showing completion or health
+
+### Accent Color Application
+- **Primary actions**: Color the most important buttons/CTAs
+- **Links**: Add color to clickable text (maintain accessibility)
+- **Icons**: Colorize key icons for recognition and personality
+- **Headers/titles**: Add color to section headers or key labels
+- **Hover states**: Introduce color on interaction
+
+### Background & Surfaces
+- **Tinted backgrounds**: Replace pure gray (`#f5f5f5`) with warm neutrals (`oklch(97% 0.01 60)`) or cool tints (`oklch(97% 0.01 250)`)
+- **Colored sections**: Use subtle background colors to separate areas
+- **Gradient backgrounds**: Add depth with subtle, intentional gradients (not generic purple-blue)
+- **Cards & surfaces**: Tint cards or surfaces slightly for warmth
+
+**Use OKLCH for color**: It's perceptually uniform, meaning equal steps in lightness *look* equal. Great for generating harmonious scales.
+
+### Data Visualization
+- **Charts & graphs**: Use color to encode categories or values
+- **Heatmaps**: Color intensity shows density or importance
+- **Comparison**: Color coding for different datasets or timeframes
+
+### Borders & Accents
+- **Accent borders**: Add colored left/top borders to cards or sections
+- **Underlines**: Color underlines for emphasis or active states
+- **Dividers**: Subtle colored dividers instead of gray lines
+- **Focus rings**: Colored focus indicators matching brand
+
+### Typography Color
+- **Colored headings**: Use brand colors for section headings (maintain contrast)
+- **Highlight text**: Color for emphasis or categories
+- **Labels & tags**: Small colored labels for metadata or categories
+
+### Decorative Elements
+- **Illustrations**: Add colored illustrations or icons
+- **Shapes**: Geometric shapes in brand colors as background elements
+- **Gradients**: Colorful gradient overlays or mesh backgrounds
+- **Blobs/organic shapes**: Soft colored shapes for visual interest
+
+## Balance & Refinement
+
+Ensure color addition improves rather than overwhelms:
+
+### Maintain Hierarchy
+- **Dominant color** (60%): Primary brand color or most used accent
+- **Secondary color** (30%): Supporting color for variety
+- **Accent color** (10%): High contrast for key moments
+- **Neutrals** (remaining): Gray/black/white for structure
+
+### Accessibility
+- **Contrast ratios**: Ensure WCAG compliance (4.5:1 for text, 3:1 for UI components)
+- **Don't rely on color alone**: Use icons, labels, or patterns alongside color
+- **Test for color blindness**: Verify red/green combinations work for all users
+
+### Cohesion
+- **Consistent palette**: Use colors from defined palette, not arbitrary choices
+- **Systematic application**: Same color meanings throughout (green always = success)
+- **Temperature consistency**: Warm palette stays warm, cool stays cool
+
+**NEVER**:
+- Use every color in the rainbow (choose 2-4 colors beyond neutrals)
+- Apply color randomly without semantic meaning
+- Put gray text on colored backgrounds—it looks washed out; use a darker shade of the background color or transparency instead
+- Use pure gray for neutrals—add subtle color tint (warm or cool) for sophistication
+- Use pure black (`#000`) or pure white (`#fff`) for large areas
+- Violate WCAG contrast requirements
+- Use color as the only indicator (accessibility issue)
+- Make everything colorful (defeats the purpose)
+- Default to purple-blue gradients (AI slop aesthetic)
+
+## Verify Color Addition
+
+Test that colorization improves the experience:
+
+- **Better hierarchy**: Does color guide attention appropriately?
+- **Clearer meaning**: Does color help users understand states/categories?
+- **More engaging**: Does the interface feel warmer and more inviting?
+- **Still accessible**: Do all color combinations meet WCAG standards?
+- **Not overwhelming**: Is color balanced and purposeful?
+
+Remember: Color is emotional and powerful. Use it to create warmth, guide attention, communicate meaning, and express personality. But restraint and strategy matter more than saturation and variety. Be colorful, but be intentional.