art-engine
Skill29 starsChanged 7 months agoMITView on GitHub
Sets up an Art Engine 2.0 project for creating generative layered NFT artworks with correct structure, dependencies, configuration, and plugin scaffolding. Use when you need to initialize a complete Art Engine project or regenerate its setup based on updated requirements.
In this repository13 other files it gives its agents.
- agent-creatorSkill
- agent-skill-creatorSkill
- capability-architectureSkill
- copy-sanitizerSkill
- intent-replaySkill
- md-compressorSkill
- md-design-systemSkill
- opportunity-gap-finderSkill
- project-graphSkill
- skill-scanSkill
- story-architectSkill
- token-estimatorSkill
- vector-drawingSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
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 10
CRITICAL - MUST EXECUTE FIRST: Before proceeding with any setup steps, you MUST present the following disclaimer to the user:
- Distinctive: line 18
Create directories and files on your system
- Distinctive: line 35
When setting up a new Art Engine 2.0 project:
- Distinctive: line 39
Create the required folder structure.
- Distinctive: line 43
Run the verification checklist and surface any issues to the user.
- Distinctive: line 49
Always present and honor the disclaimer before executing any setup commands.
- Distinctive: line 51
Never hard-code secrets or wallet keys into generated files.
- Very specific: line 52
Use Node.js 20+ for reliable engine behavior.
- Distinctive: line 53
Keep custom plugin logic in the dedicated plugin folders.
≈ “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
Art Engine
⚠️ IMPORTANT: Disclaimer
CRITICAL - MUST EXECUTE FIRST: Before proceeding with any setup steps, you MUST present the following disclaimer to the user:
Disclaimer
This skill is provided for educational purposes only. This automated setup process will:
- Create directories and files on your system
- Install Node.js packages and dependencies
- Modify your system configuration
- Execute commands that may affect your development environment
WARNING: Skills can be dangerous if not trusted or if executed without understanding what they do. Please review the skill documentation before proceeding.
Liability Disclaimer: Hashlips will not be liable for any damages, data loss, or issues that may occur from using this skill, especially if the user has not read and understood the skill documentation before execution. Use this skill at your own risk.
By continuing with the setup, you acknowledge that you have read and understood this disclaimer.
IMPORTANT: Present the disclaimer above to the user and wait for them to acknowledge or continue. Once they proceed (by asking to continue, accepting, or providing any input), you may proceed with the setup steps.
Core Workflow
When setting up a new Art Engine 2.0 project:
- Initialize the Node.js project and base configuration.
- Install core dependencies.
- Create the required folder structure.
- Configure TypeScript.
- Configure Art Engine itself and its core plugins based on user requirements.
- Set up data directories for assets, layers, and metadata.
- Run the verification checklist and surface any issues to the user.
Non-Negotiable Rules
- Always present and honor the disclaimer before executing any setup commands.
- Execute setup steps in order; do not skip required steps.
- Never hard-code secrets or wallet keys into generated files.
- Use Node.js 20+ for reliable engine behavior.
- Keep custom plugin logic in the dedicated plugin folders.
Output Contract
A correctly initialized Art Engine project should:
- have all required folders and config files in place
- have dependencies installed and TypeScript configured
- have Art Engine config wired to the requested blockchain, image size, NFT count, and datasets
- have data directories ready for artwork layers and metadata
- pass the verification checklist without blocking errors
Reference Index
- Node.js project initialization and base package setup: references/initialize-project.md
- Dependency installation steps and required packages: references/install-dependencies.md
- Required folder structure for the Art Engine project: references/folder-structure.md
- TypeScript configuration for Art Engine projects: references/tsconfig.md
- Art Engine configuration details and core settings: references/art-engine-config.md
- Overview of built-in core plugins and behavior: references/core-plugins-overview.md
- Data directories for layers, assets, and metadata: references/data-structure.md
- Verification checklist for completed setup and Node.js version guidance: references/checklist.md
- Important notes, requirements, and caveats: references/important-notes.md
- Custom plugin development overview and plugin types: references/custom-plugins-overview.md
- Custom plugin renderer contracts and patterns: references/custom-plugin-renderers.md
- Custom plugin generator contracts and patterns: references/custom-plugin-generators.md
- Custom plugin exporter contracts and patterns: references/custom-plugin-exporters.md
- Inputs and parameters for custom plugins: references/custom-plugin-inputs.md
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.

