three-js
Skill275 starsChanged 35 days agoApache-2.0View on GitHub
Expert guidance for Three.js and React Three Fiber development with modern React, TypeScript, and performance best practices
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sivaguru-2113/Agent-personatheir own version, first seen Aug 18, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sivaguru-2113/Agent-persona★ 1same name
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 repository264 other files it gives its agents.
- accessibility-a11ySkill
- alpine-jsSkill
- analytics-data-analysisSkill
- android-developmentSkill
- angular-developmentSkill
- angularSkill
- anime-jsSkill
- anthropic-claude-developmentSkill
- api-developmentSkill
- apollo-graphqlSkill
- aspnet-coreSkill
- astroSkill
- auth0-authenticationSkill
- autogen-developmentSkill
- automl-hyperparameter-optimizationSkill
- aws-developmentSkill
- azureSkill
- backend-developmentSkill
- bash-scriptingSkill
- beautifulsoup-parsingSkill
- bitbucket-workflowSkill
- blazorSkill
- blender-python-addonSkill
- blockchainSkill
- bootstrapSkill
- business-central-developmentSkill
- cheerio-parsingSkill
- chrome-extension-developmentSkill
- ci-cd-best-practicesSkill
- clean-architectureSkill
- clean-codeSkill
- clerk-authenticationSkill
- cloudflare-developmentSkill
- computer-vision-opencvSkill
- convexSkill
- cppSkill
- c-sharpSkill
- cssSkill
- cypressSkill
- data-analysis-jupyterSkill
- data-analystSkill
- data-jupyter-pythonSkill
- deep-learning-pythonSkill
- deep-learning-pytorchSkill
- deep-learningSkill
- deno-typescriptSkill
- design-systemsSkill
- devopsSkill
- django-pythonSkill
- django-rest-api-developmentSkill
- dockerSkill
- dotnetSkill
- drizzle-ormSkill
- drupal-developmentSkill
- elasticsearch-best-practicesSkill
- electron-developmentSkill
- elixirSkill
- embedded-stm32Skill
- esbuild-bundlerSkill
- ethereumSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 19 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈19
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Write concise, technical responses with accurate React examples
- Distinctive: line 16
Use functional, declarative programming.
- Distinctive: line 17
Prefer iteration and modularization over code duplication
- Distinctive: line 18
Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasRendered)
- Distinctive: line 19
Use lowercase with dashes for directories (e.g., components/auth-wizard)
- Distinctive: line 24
Use "function" keyword for pure functions.
- Distinctive: line 25
Use TypeScript for all code.
- Distinctive: line 26
Avoid enums; use maps instead
- Distinctive: line 32
Use early returns for error conditions to avoid deeply nested if statements
- Distinctive: line 33
Place the happy path last in the function for improved readability
- Distinctive: line 34
Use guard clauses to handle preconditions and invalid states early
- Distinctive: line 40
Use functional components and interfaces
- Distinctive: line 42
Use function, not const, for components
- Distinctive: line 43
Use Next UI and Tailwind CSS for components and styling
- Distinctive: line 48
Use dynamic loading for non-critical components
- Distinctive: line 55
Use object pooling for frequently created/destroyed objects
- Distinctive: line 60
Use appropriate texture sizes and formats
- Distinctive: line 65
Use the useFrame hook for animations
- Very specific: line 67
Use refs for direct Three.js object manipulation
- Distinctive: line 69
Use drei library helpers for common 3D patterns
≈ “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
Three.js Development
You are an expert in React, Vite, Tailwind CSS, Three.js, React Three Fiber, and Next UI.
Key Principles
- Write concise, technical responses with accurate React examples
- Use functional, declarative programming; avoid classes
- Prefer iteration and modularization over code duplication
- Use descriptive variable names with auxiliary verbs (e.g., isLoading, hasRendered)
- Use lowercase with dashes for directories (e.g., components/auth-wizard)
- Favor named exports for components
JavaScript/TypeScript Standards
- Use "function" keyword for pure functions; omit semicolons
- Use TypeScript for all code; prefer interfaces over types
- Avoid enums; use maps instead
- File structure: Exported component, subcomponents, helpers, static content, types
Error Handling and Validation
- Handle errors and edge cases at the beginning of functions
- Use early returns for error conditions to avoid deeply nested if statements
- Place the happy path last in the function for improved readability
- Use guard clauses to handle preconditions and invalid states early
- Implement proper error logging and user-friendly error messages
React Best Practices
Component Guidelines
- Use functional components and interfaces
- Use declarative JSX
- Use function, not const, for components
- Use Next UI and Tailwind CSS for components and styling
- Implement responsive design with Tailwind CSS
Performance Optimization
- Wrap client components in Suspense with fallback
- Use dynamic loading for non-critical components
- Optimize images: WebP format, size data, lazy loading
Three.js Specific Guidelines
Scene Management
- Properly dispose of geometries, materials, and textures when no longer needed
- Use object pooling for frequently created/destroyed objects
- Implement level of detail (LOD) for complex scenes
Performance
- Minimize draw calls through geometry merging and instancing
- Use appropriate texture sizes and formats
- Implement frustum culling for large scenes
- Profile and optimize render loops
React Three Fiber
- Use the useFrame hook for animations
- Leverage useThree for accessing the Three.js context
- Use refs for direct Three.js object manipulation
- Implement proper cleanup in useEffect hooks
- Use drei library helpers for common 3D patterns
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.

