clean-frontend-scaffolding
Skill7 starsChanged 17 days agoMITView on GitHub
Use when a freshly scaffolded Vite app still has the demo App, default styles, sample assets and placeholder title; reduces them to a minimal shell before real structure is added.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- VelimirMueller/ai-development-skillsword for word, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- VelimirMueller/ai-development-skills★ 7100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository156 other files it gives its agents.
- skills/swift/swiftui-design-principles/AGENTS.mdAGENTS.md
- skills/swift/ios-code-audit/CLAUDE.mdCLAUDE.md
- skills/swift/swift-focusengine-pro/llms.txtllms.txt
- build-llm-seamSkill
- build-mcp-serverSkill
- build-rag-pipelineSkill
- secure-llm-featuresSkill
- set-up-llm-evalsSkill
- build-nextjs-backendSkill
- build-supabase-edge-functionSkill
- configure-backend-testsSkill
- design-http-apiSkill
- harden-backendSkill
- scaffold-fastapi-serviceSkill
- scaffold-go-serviceSkill
- scaffold-hono-serviceSkill
- secure-supabase-rlsSkill
- set-up-backend-authSkill
- set-up-background-jobsSkill
- set-up-databaseSkill
- set-up-nextjs-supabase-authSkill
- set-up-observabilitySkill
- set-up-supabaseSkill
- build-cliSkill
- release-cliSkill
- set-up-dev-toolchainSkill
- audit-securitySkill
- audit-toolchainSkill
- extend-skillsetSkill
- promote-releaseSkill
- set-up-stack-profileSkill
- write-commit-messagesSkill
- write-pull-requestsSkill
- analyze-complexitySkill
- apply-algorithmsSkill
- apply-design-patternsSkill
- apply-design-principlesSkill
- apply-solidSkill
- choose-data-structureSkill
- debug-systematicallySkill
- enforce-dependency-ruleSkill
- refactor-safelySkill
- slice-and-estimateSkill
- write-clean-testsSkill
- write-readable-codeSkill
- configure-accessibilitySkill
- configure-analyticsSkill
- configure-ciSkill
- configure-error-trackingSkill
- configure-lintingSkill
- configure-test-stackSkill
- configure-typescriptSkill
- create-moduleSkill
- optimize-performanceSkill
- scaffold-frontend-projectSkill
- set-up-authSkill
- set-up-design-systemSkill
- set-up-document-headSkill
- set-up-error-boundariesSkill
- set-up-feature-flagsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read .claude/stack-profile.md if present: frontend.framework (react | vue) decides the branch.
- Distinctive: line 12
Look for the markers of the create-vite templates (Vite 8):
- Distinctive: line 19
If none of these exist or match, exit early with: "Scaffold cleanup not needed — files appear customized."
- Distinctive: line 23
All scaffold defaults present → full clean (proceed to step 3).
- Very specific: line 54
Delete src/App.css; the reduced App.tsx no longer imports it, and nothing else does.
- Very specific: line 61
Delete src/assets/ (hero.png, react.svg, vite.svg) and public/icons.svg (the demo's social-icon sprite).
- Very specific: line 62
Update index.html <title> (Vite + React + TS) to the project name (ask via AskUserQuestion if unknown).
- Very specific: line 86
Delete src/assets/ (hero.png, vite.svg, vue.svg), public/icons.svg and src/components/HelloWorld.vue.
- Very specific: line 87
Update index.html <title> (Vite + Vue + TS) to the project name.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Clean Frontend Scaffolding
1. Audit current state
Read .claude/stack-profile.md if present: frontend.framework (react | vue) decides the branch; otherwise detect it from package.json (react or vue in dependencies). frontend.meta of nuxt or next → exit; those scaffolds have their own layout.
Look for the markers of the create-vite templates (Vite 8):
grep -l "assets/hero.png\|assets/react.svg\|assets/vue.svg\|HelloWorld\|Get started" src/App.* src/components/*.vue 2>/dev/null
grep -l "Vite + " index.html 2>/dev/null # <title>Vite + React + TS</title>
ls src/assets src/App.css public 2>/dev/null # hero.png, react.svg, vue.svg, vite.svg, favicon.svg, icons.svgIf none of these exist or match, exit early with: "Scaffold cleanup not needed — files appear customized."
2. Decide what to do
- All scaffold defaults present → full clean (proceed to step 3).
- Partially customized → remove only the default items still present.
- Already customized → exit.
3. Purge boilerplate
React
Reduce
src/App.tsxto:export default function App() { return <div>App shell</div>; }Reduce
src/main.tsxto a clean root render:import { StrictMode } from 'react'; import { createRoot } from 'react-dom/client'; import App from './App'; import './index.css'; createRoot(document.getElementById('root')!).render( <StrictMode> <App /> </StrictMode>, );- Delete
src/App.css; the reducedApp.tsxno longer imports it, and nothing else does. Replace
src/index.csscontent with the Tailwind v4 import (v4 dropped the three@tailwinddirectives for a single@import):@import "tailwindcss";- Delete
src/assets/(hero.png,react.svg,vite.svg) andpublic/icons.svg(the demo's social-icon sprite). Keeppublic/favicon.svguntil the project has its own icon; it is the Vite logo. - Update
index.html<title>(Vite + React + TS) to the project name (ask via AskUserQuestion if unknown).
Vue
Reduce
src/App.vueto:<script setup lang="ts"></script> <template> <div>App shell</div> </template>Reduce
src/main.tsto:import { createApp } from 'vue'; import App from './App.vue'; import './style.css'; createApp(App).mount('#app');- Replace
src/style.csswith the Tailwind v4 import only (see React step 4). - Delete
src/assets/(hero.png,vite.svg,vue.svg),public/icons.svgandsrc/components/HelloWorld.vue. Keeppublic/favicon.svguntil the project has its own icon. - Update
index.html<title>(Vite + Vue + TS) to the project name.
4. Verify
pnpm devExpected: dev server starts; visiting the app shows the empty shell with no console errors. Stop the server. pnpm build must also pass: it runs tsc -b/vue-tsc -b, which catches an import of a deleted asset.
References
- ./boilerplate-removal.md — exact files and patterns per framework, with examples and anti-patterns.
- ../_shared/conventions.md — path alias and source-root conventions.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

