Adrienenjalbert/safe-refactor
nextjs-app/ai-src/skills/safe-refactor/SKILL.md
Use when refactoring existing code, moving files, normalizing structure, or improving architecture without changing user-visible behavior in this repo.
development
Updated Apr 21, 2026
$ install --global
skillsauthnpx skillsauth add Adrienenjalbert/flex-carrer-hub safe-refactorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 3:00 AM83.9s1 file scanned
SKILL.md
- name:
- safe-refactor
- description:
- Use when refactoring existing code, moving files, normalizing structure, or improving architecture without changing user-visible behavior in this repo.
Safe Refactor
Use When
- moving code between folders
- shrinking large route files
- aligning old code to the current architecture
- cleaning up imports or ownership boundaries
Main Rule
Preserve behavior first. Improve structure second.
Required Approach
- identify the current behavior and public route impact
- keep route/API/SEO behavior unchanged
- move composition into the correct feature layer
- reuse existing shells/helpers instead of inventing replacements
- stop when the task goal is met
Architecture Targets
- thin
src/app - feature-owned logic in
src/features - no new feature data in
src/lib - no new feature UI in retired locations
Do Not Refactor Opportunistically
Do not do these during an unrelated task:
- broad folder normalization
- mass renames across untouched domains
- replacing active shared abstractions just because they are imperfect
Current Reality To Respect
These are still active:
src/features/career-hub/shared/*src/components/common/*
Do not treat them as dead code by default.
Success Criteria
- behavior preserved
- route files thinner if that was part of the task
- file placement improved
- no architecture regression introduced
Related Skills
Adrienenjalbert/verification-checklist
development
VerifiedTrustedCommunity
Use when finishing a code change, validating generated code, or deciding which repo checks must run before presenting work in this repo.
SKILL.mdUpdated Apr 21, 2026
Adrienenjalbert/tool-page-builder
tools
VerifiedTrustedCommunity
Use when creating or editing Career Hub tool pages, calculator pages, tool metadata, tool registry entries, or tool-specific support sections in this repo.
SKILL.mdUpdated Apr 21, 2026
Adrienenjalbert/seo-page-rules
data-ai
VerifiedTrustedCommunity
Use when editing public pages, metadata, canonical URLs, structured data, sitemaps, robots rules, or any SEO-sensitive behavior in this repo.
SKILL.mdUpdated Apr 21, 2026
Adrienenjalbert/nextjs-app/ai-src/skills/repo-best-practices
tools
VerifiedTrustedCommunity
--- name: repo-best-practices description: Use when generating or reviewing code in this repo to match the codebase’s existing implementation habits: reuse-first, no duplication, config-driven content, selector helpers, typed configs, shared shells, and minimal custom patterns. --- # Repo Best Practices ## Use When - generating new code - editing existing code - reviewing whether generated code feels native to the repo - deciding whether to reuse, extract, or inline something ## Main Princip
SKILL.mdUpdated Apr 21, 2026