dev-booster 1.1.0 → 1.1.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-booster",
-  "version": "1.1.0",
+  "version": "1.1.2",
   "description": "Reusable AI development kit with manual boosters, governance, and project bootstrap",
   "type": "module",
   "scripts": {

package/src/index.js

@@ -11,6 +11,12 @@ const TEMPLATE_DIR = path.resolve(__dirname, '..', 'template')
 // Destination: the user's current working directory (where they ran npx)
 const TARGET_DIR = process.cwd()
 const args = process.argv.slice(2)
+const GITIGNORE_BLOCK = [
+  '# DEV-BOOSTER',
+  '.devbooster/',
+  'DEVBOOSTER_INIT.md',
+]
+const GITIGNORE_MARKER = '# DEV-BOOSTER'
 const IDE_BRIDGE_BLOCK = [
   '# 🤖 DEV BOOSTER — AGENTIC KIT BOOTSTRAP',
   '',
@@ -70,16 +76,16 @@ function ensureTrailingNewline(content) {
   return content.endsWith('\n') ? content : `${content}\n`
 }
 
-function appendUniqueLines(filePath, lines) {
+function appendUniqueBlock(filePath, blockLines, marker) {
   const existing = fs.existsSync(filePath) ? fs.readFileSync(filePath, 'utf8') : ''
-  const normalized = ensureTrailingNewline(existing)
-  const missingLines = lines.filter((line) => !existing.includes(line))
-
-  if (missingLines.length === 0) {
+  if (existing.includes(marker)) {
     return false
   }
 
-  const nextContent = `${normalized}${missingLines.join('\n')}\n`
+  const trimmedEnd = existing.replace(/\s*$/, '')
+  const prefix = trimmedEnd.length > 0 ? `${trimmedEnd}\n\n` : ''
+  const nextContent = `${prefix}${blockLines.join('\n')}\n`
+  fs.mkdirSync(path.dirname(filePath), { recursive: true })
   fs.writeFileSync(filePath, nextContent)
   return true
 }
@@ -117,29 +123,16 @@ async function maybeAddDevBoosterToGitignore() {
   }
 
   const gitignorePath = path.join(TARGET_DIR, '.gitignore')
-  const changed = appendUniqueLines(gitignorePath, ['.devbooster/', 'DEVBOOSTER_INIT.md'])
+  const changed = appendUniqueBlock(gitignorePath, GITIGNORE_BLOCK, GITIGNORE_MARKER)
 
   console.log('▸ .gitignore')
   if (changed) {
     console.log('  status: updated')
-    console.log('  entries: .devbooster/, DEVBOOSTER_INIT.md\n')
+    console.log('  entries: # DEV-BOOSTER, .devbooster/, DEVBOOSTER_INIT.md\n')
   } else {
     console.log('  status: already configured')
-    console.log('  entries: .devbooster/, DEVBOOSTER_INIT.md\n')
-  }
-}
-
-function appendUniqueBlock(filePath, blockLines, marker) {
-  const existing = fs.existsSync(filePath) ? fs.readFileSync(filePath, 'utf8') : ''
-  if (existing.includes(marker)) {
-    return false
+    console.log('  entries: # DEV-BOOSTER, .devbooster/, DEVBOOSTER_INIT.md\n')
   }
-
-  const normalized = ensureTrailingNewline(existing)
-  const nextContent = `${normalized}${blockLines.join('\n')}\n`
-  fs.mkdirSync(path.dirname(filePath), { recursive: true })
-  fs.writeFileSync(filePath, nextContent)
-  return true
 }
 
 function writeIdeBridgeFallbackFlag() {

package/template/.devbooster/hub/skills/react-file-organization/SKILL.md

@@ -0,0 +1,251 @@
+---
+name: react-file-organization
+description: Personal React file organization style for restructuring imports, component sections, and local formatting without changing behavior.
+allowed-tools: Read, Write, Edit
+version: 1.0
+priority: OPTIONAL
+---
+
+# React File Organization
+
+> **Optional personal skill** - Use this when the goal is to reorganize a React file according to a strict structural preference, without changing behavior.
+
+---
+
+## Goal
+
+Organize a React file following the rules below.
+
+**Do not change functionality.**
+Only reorganize structure, imports, and presentation where the rules explicitly allow it.
+
+This skill is intentionally opinionated and personal.
+It is meant to make the file "feel right" for this specific organization style, not to enforce a universal best practice.
+
+---
+
+## Activation Behavior
+
+If the user invokes this skill by name without clearly providing the target file:
+
+- do not start reorganizing anything yet
+- do not guess the file automatically
+- confirm that the skill is ready
+- ask which React file should be organized
+
+Use a short response such as:
+
+```md
+Skill `react-file-organization` loaded.
+
+I can reorganize a React file using this personal structure style without changing behavior.
+
+Which file should I organize?
+```
+
+Only proceed after the user provides the target file or a clear file reference.
+
+---
+
+## Safe Operating Mode
+
+Apply this skill only when all of the following are true:
+
+- the target is clearly a React file (`.tsx`, `.jsx`, or a React component file)
+- the file can be reorganized without changing runtime behavior
+- hooks, requests, and local declarations are already at top level of the component body
+- the requested change is organizational, not functional
+
+If the file does **not** fit this structure:
+- do **not** force the full pattern
+- do **not** invent missing sections
+- do **not** convert APIs or libraries
+- do **not** move code in a way that changes execution order or semantics
+
+If there is any real risk of behavioral change, stop and explain which part is unsafe to reorder.
+
+---
+
+## Applicability Rules
+
+- If the file does not use `Formik`, skip the `Formik` section entirely.
+- If the file does not use `React.useEffect`, do not invent one.
+- If the file does not use API hooks, skip request grouping.
+- If the file does not use `lucide-react`, do not replace another icon library automatically.
+- If the file does not use `zustand`, do not create fake hook groupings just to fit the pattern.
+- If there are no multiline imports, do not create them artificially.
+- If the file already follows another stable organization style and reorganizing it would create churn without benefit, keep the file mostly as-is.
+
+---
+
+## Hard Safety Stops
+
+Do **not** use this skill to:
+
+- rewrite business logic
+- rename functions, variables, or props unless strictly required for organization and clearly safe
+- convert component style (`function` ↔ `const`)
+- change hook dependencies
+- move hooks across conditional logic
+- move declarations in ways that can affect hoisting, closures, or side effects
+- remove comments that carry important business or implementation context
+- delete code unless it is clearly unused import noise or dead commented-out code with no project value
+
+When in doubt, prefer partial organization over risky cleanup.
+
+---
+
+## 1. Import Structure
+
+```typescript
+import React from 'react' // always first
+
+// mandatory blank line
+
+// default imports (without {}) - smaller → larger by the imported identifier
+import Input from '@/components/commons/input'
+import CpfMask from '@/masks/cpf.mask'
+import useUserStore from '@/zustand/user.store'
+
+// mandatory blank line
+
+// named imports with {} - smaller → larger by the content inside the braces
+import { api } from '@/trpc/react'
+import { toast } from 'sonner'
+import { Button } from '@/components/ui/button'
+import { useFormik } from 'formik'
+import { Eye, EyeOff, Plus } from 'lucide-react'
+
+// mandatory blank line
+
+// multiline imports - each block separated by a blank line
+import {
+  Select,
+  SelectContent,
+  SelectItem,
+} from '@/components/ui/select'
+
+// mandatory blank line
+
+import {
+  Dialog,
+  DialogContent,
+} from '@/components/ui/dialog'
+
+// mandatory blank line
+
+// imports with * or type - always last
+import * as Yup from 'yup'
+```
+
+---
+
+## 2. Internal Component Structure
+
+```typescript
+const Component: React.FC = () => {
+  // 1. React.useState - larger → smaller by line length
+  const [showPassword, setShowPassword] = React.useState<boolean>(false)
+  const [loading, setLoading] = React.useState(false)
+
+  // 2. imported hook function destructuring
+  const { modalState, setModal } = useModalStore()
+  const { setLoading } = useLoadingStore()
+  const { dbUser } = useUserStore()
+
+  // 3. API requests
+  // GET requests first
+  const { data: users } = api.user.getAll.useQuery()
+  const { data: positions } = api.position.getAll.useQuery()
+
+  // mutation requests second
+  const { mutateAsync: createUser } = api.user.create.useMutation()
+
+  // 4. Formik
+  const formik = useFormik({ ... })
+
+  // 5. custom functions
+  const handleSubmit = React.useMemo(() => { ... }, [])
+
+  // 6. React.useEffect
+  React.useEffect(() => { ... }, [])
+
+  // 7. return
+  return (...)
+}
+```
+
+---
+
+## 3. Icon Rules
+
+- Always use `size={}` instead of sizing only with `className`
+- Never place icons inside buttons for this organization style
+- Always import icons from `lucide-react`
+
+```typescript
+// correct
+<Eye size={20} />
+
+// wrong
+<button><Eye className="w-5 h-5" /></button>
+```
+
+---
+
+## 4. General Rules
+
+- Always respond in Portuguese
+- Always keep spacing between import groups
+- Remove unused imports when clearly safe
+- Remove commented code only when it is clearly dead noise and not useful documentation
+- Do not change behavior, only organize
+- Follow the order even when some sections do not exist
+- If a section does not exist in the file, skip it naturally
+- If a rule conflicts with file safety, preserve safety first
+
+---
+
+## 5. Sorting Criteria
+
+### Default Imports
+
+Count the imported identifier before `from`:
+
+```typescript
+import Input from '@/components/commons/input'
+import useModalStore from '@/zustand/modal.store'
+import useLoadingStore from '@/zustand/loading.store'
+```
+
+### Named Imports
+
+Count the content inside `{}`:
+
+```typescript
+import { api } from '@/trpc/react'
+import { Button } from '@/components/ui/button'
+import { Eye, EyeOff } from 'lucide-react'
+```
+
+---
+
+## Execution Prompt
+
+Use this command when applying the skill:
+
+**"Organize this React file following exactly all rules from the prompt above. Do not change behavior, only reorganize."**
+
+If needed, you may also use this safer variant:
+
+**"Organize this React file using the react-file-organization skill. Apply the style only where it is safe, skip missing sections naturally, and do not change behavior."**
+
+---
+
+## Notes
+
+- This skill is intentionally opinionated.
+- It is not a global Dev Booster rule.
+- It should not be auto-loaded by any booster.
+- Use it only when this exact organization style is desired.
+- Prefer making the user happy over forcing mechanical symmetry.