القائمة
Initialize a new project by cloning magoz/init template, configuring tech stack, and cleaning unused services.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | init |
| description | Initialize a new project by cloning magoz/init template, configuring tech stack, and cleaning unused services. |
Initialize a new project by cloning the magoz/init template, then configuring the tech stack by removing unused services.
If the user didn't provide a project name as an argument, ask:
What's the project name?
Use the name as-is for the directory and repo name (kebab-case recommended).
gh repo create <project-name> --template magoz/init --private --clone
Then cd into the new directory. All subsequent operations happen inside it.
pnpm install
cp .env.example .env.local
Update package.json name to match the project name.
Ask a single open question:
What are you building?
Wait for the user's response. This informs cleanup decisions.
Ask each question explicitly. Yes/No answers.
| If removing... | Also remove... | Note |
|---|---|---|
| Database | Auth | Auth requires db for user storage |
| Telegram | Activity | Activity logs to Telegram |
If user wants auth but said no to database, clarify:
"Auth requires a database. Should I enable the database?"
Remove unused services silently based on answers.
| Service | Remove if "no" to... |
|---|---|
| Db | "database" |
| Auth | "accounts/login" |
| "emails" | |
| S3 | "file uploads" |
| Telegram | "admin notifications" |
| Activity | "admin notifications" (depends on Telegram) |
| Telemetry | "error tracking" |
lib/services/db/
drizzle.config.ts
lib/services/db/migrations/
Also:
Db.Live from lib/layers.tsDATABASE_URL from .env.example and .env.localpackage.jsondrizzle-orm and drizzle-kit from dependencieslib/services/auth/
app/(auth)/
app/api/auth/
Also:
Auth.Live from lib/layers.tsBETTER_AUTH_SECRET from .env.example and .env.localbetter-auth from dependencieslib/services/email/
Also:
Email.Live from lib/layers.tsRESEND_API_KEY, EMAIL_SENDER from .env.example and .env.localresend from dependencieslib/services/s3/
lib/core/file/
Also:
S3.Live from lib/layers.tsAWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_REGION, AWS_S3_BUCKET from .env.example and .env.local@aws-sdk/client-s3, @aws-sdk/s3-request-presigner from dependencieslib/services/telegram/
Also:
Telegram.Live from lib/layers.tsTELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID from .env.example and .env.locallib/services/activity/
Also:
Activity.Live from lib/layers.tslib/services/telemetry/
instrumentation.ts
instrumentation-client.ts
sentry.edge.config.ts
sentry.server.config.ts
Also:
TelemetryLayer from lib/layers.tsSENTRY_PROJECT, SENTRY_AUTH_TOKEN, NEXT_PUBLIC_SENTRY_DSN, NEXT_PUBLIC_POSTHOG_KEY from .env.example and .env.local@sentry/nextjs, posthog-js from dependenciesnext.config.tsFor each service to remove:
lib/layers.ts: remove import + remove from Layer.mergeAll(...).env.example and .env.local: remove relevant env varspackage.json: remove dependencies and scriptspnpm install after dependency changesRemove example code that references removed services (e.g., lib/core/post/ if it uses removed services).
Commit:
git add -A
git commit -m "chore: remove unused services"
Summarize:
Cleaned up the codebase:
- Removed: S3, Telegram, Activity
- Kept: Database, Auth, Email, Telemetry
README.md with project name and descriptionpnpm dev to verify everything worksgit add -A
git commit -m "chore: init project"
Project initialized!
Tech stack: [list of enabled services] Next:
pnpm devto start developing
If /init is run on a project that already has services configured:
lib/services/ has been modified from templateCouldn't commit changes. Please commit manually:
git add -A && git commit -m "chore: init project"
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.
Create a custom skill for this project. Determines skill type, writes SKILL.md (and optional references/scripts) to .opencode/skills/<name>/, commits and pushes. Load FIRST before writing any skill.
Import a bitmap image (PNG/JPEG/GIF) from a URL into a Figma file as a frame. Use whenever an image needs to land in Figma — AI mockups, photos, renders, artwork, screenshots. Bypasses use_figma sandbox limits that block the obvious paths (fetch, atob, createImageAsync, REST upload). If you skip this skill and try the obvious paths, you will lose 30+ minutes. Triggers on: import image to Figma, add image to Figma, put image in Figma, Figma image import, bitmap to Figma.
Generate images, videos, and music using AI models (Imagen, Flux, Veo, Runway, Kling, Sora, Suno, ElevenLabs, etc.). Use when user asks to create, generate, edit, upscale, or produce any visual or audio media.
Install a skill from a GitHub URL or local path. Copies SKILL.md (and references/scripts) into the project's .opencode/skills/ directory and creates the companion command. Use when user wants to add an existing skill to their project.
Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.js files.