Use this after a developer has run eve init and needs to configure the project for Eve Horizon.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioneve-new-project-setupExecute the skills CLI command in your project's root directory to begin installation:
Fetches eve-new-project-setup from incept5/eve-skillpacks and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate eve-new-project-setup. Access via /eve-new-project-setup in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
0
upvotes
Run in your terminal
0
installs
0
this week
—
stars
Use this after a developer has run eve init and needs to configure the project for Eve Horizon.
The user has already run:
npm install -g @eve-horizon/cli
eve init my-project
cd my-project
This skill handles the remaining setup: profile, authentication, org/project registration, manifest customization, and git remote configuration.
eve --version
If this fails, the CLI wasn't installed. Have them run:
npm install -g @eve-horizon/cli
Create a profile for the staging environment:
eve profile create staging --api-url https://api.eh1.incept5.dev
eve profile use staging
Ask the user for their email and set defaults:
eve profile set --default-email [email protected]
Check current auth status:
eve auth status
If not authenticated, log in:
eve auth login
The CLI will guide them through SSH key discovery (can fetch from GitHub if needed).
We'll set harness credentials after project creation.
Ask the user for:
Create or ensure they exist:
eve org ensure my-company --slug myco
eve project ensure --name "My App" --slug my-app --repo-url [email protected]:me/my-app.git --branch main
URL impact: The org and project slugs directly form deployment URLs and K8s namespaces:
{service}.{orgSlug}-{projectSlug}-{env}.{domain} (e.g., api.myco-my-app-staging.eh1.incept5.dev)eve-{orgSlug}-{projectSlug}-{env} (e.g., eve-myco-my-app-staging)${ORG_SLUG} is available for interpolation in manifest valuesSlugs are immutable — choose short, meaningful values.
Set as defaults in the profile:
eve profile set --org org_xxx --project proj_xxx
Ask which harness they want to target (can be more than one):
Map harnesses to required secrets:
ANTHROPIC_API_KEY (preferred) or Claude OAuth via eve auth syncOPENAI_API_KEY (preferred) or CODEX_AUTH_JSON_B64Z_AI_API_KEYGEMINI_API_KEY (or GOOGLE_API_KEY)Decide where to store secrets:
Use a secrets file for batch setup (starter repo includes secrets.env.example):
cp secrets.env.example secrets.env
eve secrets import --org org_xxx --file ./secrets.env
For Claude/Codex OAuth tokens on the host:
# Store OAuth tokens in the project scope (or add --system if admin)
eve auth sync --project proj_xxx
The starter template includes .eve/manifest.yaml. Update it with the project details:
schema: eve/compose/v2
project: my-app
services:
api:
build:
context: apps/api
ports: [3000]
x-eve:
ingress:
public: true
port: 3000
environments:
staging:
pipeline: deploy
pipelines:
deploy:
steps:
- name: deploy
action: { type: deploy }
Key fields to customize:
project: Match the project slugservices: Define your app's servicesx-eve.ingress: Configure public accessThe project starts with no remote. Help set one up:
git remote -v
git remote add origin [email protected]:user/my-app.git
git push -u origin main
Run these checks to confirm setup:
eve system health
eve auth status
eve profile show
After setup is complete, suggest:
docker compose up --buildeve secrets set MY_KEY "value" or eve secrets import --file ./secrets.enveve env deploy staging --ref main --repo-dir .eve job create --prompt "Review the codebase"Note: If the environment has a pipeline configured in the manifest, eve env deploy <env> --ref <sha> will trigger that pipeline. Use --direct to bypass the pipeline and do a direct deploy. --ref must be a 40-character SHA, or a ref resolved against --repo-dir/cwd.
npm install -g @eve-horizon/cli
eve auth login
eve profile create staging --api-url https://api.eh1.incept5.dev
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend eve-new-project-setup for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
eve-new-project-setup reduced setup friction for our internal harness; good balance of opinion and flexibility.
eve-new-project-setup is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added eve-new-project-setup from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in eve-new-project-setup — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added eve-new-project-setup from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: eve-new-project-setup is focused, and the summary matches what you get after install.
Registry listing for eve-new-project-setup matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: eve-new-project-setup is the kind of skill you can hand to a new teammate without a long onboarding doc.
eve-new-project-setup has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 49