dev-booster 1.1.2 → 1.1.4

package/package.json

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

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

@@ -1,6 +1,6 @@
 ---
 name: react-file-organization
-description: Personal React file organization style for restructuring imports, component sections, and local formatting without changing behavior.
+description: Personal React and Next.js file organization style for restructuring imports, component sections, and local formatting without changing behavior.
 allowed-tools: Read, Write, Edit
 version: 1.0
 priority: OPTIONAL
@@ -70,11 +70,12 @@ If there is any real risk of behavioral change, stop and explain which part is u
 
 - 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 the file does not use API hooks or async access logic, skip request grouping.
+- If the file does not use one specific icon library, preserve the current icon approach instead of forcing a replacement.
+- If the file does not use `zustand`, context hooks, or external hooks, 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.
+- If the file uses `fetch`, route handlers, server actions, service calls, or request helpers instead of hook-based data access, group them under the same "data access / requests" concept without forcing a specific library pattern.
 
 ---
 
@@ -106,15 +107,18 @@ import React from 'react' // always first
 import Input from '@/components/commons/input'
 import CpfMask from '@/masks/cpf.mask'
 import useUserStore from '@/zustand/user.store'
+import getUserLabel from '@/lib/user-label'
 
 // mandatory blank line
 
 // named imports with {} - smaller → larger by the content inside the braces
 import { api } from '@/trpc/react'
+import { revalidatePath } from 'next/cache'
 import { toast } from 'sonner'
 import { Button } from '@/components/ui/button'
 import { useFormik } from 'formik'
 import { Eye, EyeOff, Plus } from 'lucide-react'
+import { useQuery } from '@tanstack/react-query'
 
 // mandatory blank line
 
@@ -144,30 +148,27 @@ import * as Yup from 'yup'
 
 ```typescript
 const Component: React.FC = () => {
-  // 1. React.useState - larger → smaller by line length
+  // 1. React local hooks
   const [showPassword, setShowPassword] = React.useState<boolean>(false)
   const [loading, setLoading] = React.useState(false)
 
-  // 2. imported hook function destructuring
+  // 2. external hooks / store hooks / context hooks
   const { modalState, setModal } = useModalStore()
   const { setLoading } = useLoadingStore()
   const { dbUser } = useUserStore()
 
-  // 3. API requests
-  // GET requests first
+  // 3. data hooks / requests / async access layer
   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
+  // 4. form state
   const formik = useFormik({ ... })
 
-  // 5. custom functions
+  // 5. derived values / custom functions / handlers
   const handleSubmit = React.useMemo(() => { ... }, [])
 
-  // 6. React.useEffect
+  // 6. effects
   React.useEffect(() => { ... }, [])
 
   // 7. return
@@ -179,16 +180,15 @@ const Component: React.FC = () => {
 
 ## 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`
+- If the file already uses an icon library consistently, preserve it instead of forcing a replacement
 
 ```typescript
-// correct
-<Eye size={20} />
+// preferred for this style
+<Eye />
 
-// wrong
-<button><Eye className="w-5 h-5" /></button>
+// avoid this pattern in this organization style
+<button><Eye /></button>
 ```
 
 ---
@@ -199,10 +199,13 @@ const Component: React.FC = () => {
 - 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
+- If section comments are kept after reorganization, rename them to generic and readable labels
+- Prefer labels such as `React Hooks`, `External Hooks`, `Data Access / Requests`, `Form State`, `Custom Functions`, `Effects`
 - 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
+- Organize by structural role in the file, not by forcing one exact technology choice
 
 ---
 
@@ -230,6 +233,43 @@ import { Eye, EyeOff } from 'lucide-react'
 
 ---
 
+## Validation After Reorganization
+
+After reorganizing the file, run the lightest relevant validation available in the project.
+
+Preferred order:
+
+1. `typecheck`
+2. `lint`
+3. `check`
+
+If these scripts exist in `package.json`, prefer them in that order.
+
+Examples:
+
+```bash
+npm run typecheck
+npm run lint
+npm run check
+```
+
+Rules:
+
+- choose the most relevant and least destructive validation first
+- do not invent commands that the project does not have
+- if no validation script exists, say that the file was reorganized but no automatic validation was available
+- if validation fails, report the failure clearly instead of pretending the reorganization is complete
+- if validation fails because of the reorganization pass, read the error, fix the issue, and validate again
+- only auto-fix issues that were introduced by the reorganization itself
+- do not expand into unrelated project cleanup just because validation exposed older problems
+- if the remaining failure is pre-existing or not clearly caused by the reorganization, stop and explain it clearly
+
+Goal:
+
+- confirm that the organization pass did not break imports, types, or basic project rules
+
+---
+
 ## Execution Prompt
 
 Use this command when applying the skill:

package/template/DEVBOOSTER_INIT.md

@@ -52,6 +52,9 @@ After all files have been overwritten, report back to the user with:
 - Whether the IDE bridge was already handled by the CLI or whether `AGENTS.md` had to be created as fallback.
 - Any gaps or missing information that could not be auto-detected and may need manual input.
 
+The completion report shown in chat must follow the global language configured for the active LLM/environment.
+The generated project artifacts and technical file contents may remain in technical English when appropriate.
+
 ---
 
 > [!NOTE]