Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

project-orientation

Estrelas36

Forks1

Atualizado17 de julho de 2026 às 12:02

Orient Claude to the svelteflare monorepo before starting any task. Use this skill whenever the user says "orient yourself", "explain the repo", "what's the structure here", or kicks off a task where knowing where things live matters. Also invoke it proactively at the start of a new session in this repo — it saves repeated filesystem spelunking and gives you the full picture in one read.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

pinebasedev

pinebasedev/svelteflare

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

Mais deste repositório

mesmo repositório

ui-and-theme

pinebasedev/svelteflare

Frontend/design system skill for the svelteflare monorepo. Use this whenever the user wants to build or modify UI — pages, sections, components, layouts, forms, cards, tables, dialogs, dashboards, or landing pages. Also invoke for anything theme-related: light/dark mode, custom colors, design tokens, typography, or spacing. Trigger on "add a [card/table/dialog/form/dashboard]", "build a [landing/marketing] section", "change the theme", "add dark mode", "customize colors", "install [shadcn component]", "make it look like X", "style this", "create a [component]". When in doubt, invoke — this skill prevents hard-coded colors, raw HTML elements, and design inconsistencies.

2026-07-1736

auth-db-billing

pinebasedev/svelteflare

Backend product systems skill for the svelteflare monorepo. Invoke whenever the user wants to work with auth, sessions, protected routes, users, the database, schema changes, migrations, Stripe billing, subscriptions, paid feature gates, or any server-only logic in the Hono API. Trigger on "add a protected route", "gate this behind a subscription", "add a DB column", "run migrations", "how do I check if the user is logged in", "add a new table", "wire up Stripe checkout", "check the user's plan", "add a role check", "add server-only logic", or any mention of better-auth, drizzle, D1, or Stripe. When in doubt, invoke — this skill prevents auth bypasses, wrong DB access patterns, and billing logic landing in the wrong layer.

2026-07-1636

build-feature

pinebasedev/svelteflare

Main orchestration skill for adding features to the svelteflare monorepo. Invoke whenever the user wants to add, build, implement, or create any new functionality — a page, API endpoint, DB table, form, component, auth-gated route, billing feature, or any combination. Trigger on "add X", "build X", "implement X", "I want X to do Y", "create a [page/endpoint/form/feature]", "wire up X", "make it so users can X". When in doubt, invoke — it's better to orchestrate than to start coding blind in a multi-layer monorepo.

2026-07-1636

forms

pinebasedev/svelteflare

Form handling skill for the svelteflare monorepo. Use this whenever the user wants to add, build, or modify any form — login forms, settings forms, profile editors, onboarding flows, multi-step wizards, or any input that validates and submits data. Covers the full stack: Zod schema, superforms setup, FormSnap field components, field-level errors, loading/success/error states, and toast feedback. Trigger on "add a form", "build a form for X", "create a settings page", "add a field", "handle form submission", "validate input", "show errors", "wire up a form to the API". When in doubt, invoke — this skill prevents inconsistent patterns, missing validation, and broken error handling.

2026-07-1636

svelte-core-bestpractices

pinebasedev/svelteflare

Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.

2026-07-1636

name	project-orientation
description	Orient Claude to the svelteflare monorepo before starting any task. Use this skill whenever the user says "orient yourself", "explain the repo", "what's the structure here", or kicks off a task where knowing where things live matters. Also invoke it proactively at the start of a new session in this repo — it saves repeated filesystem spelunking and gives you the full picture in one read.

Svelteflare — Project Orientation

This orientation is for you, the agent — don't recite it to the user. The user is a non-technical founder: when they ask about the project, translate to plain language (what the app does and where things stand, not ports, packages, or file paths). The non-negotiable UI/theme rules live in the root AGENTS.md — read them before any UI work.

Architecture

Two-layer Cloudflare stack:

Layer	Package	Port	Tech
API	`@repo/api`	9003	Hono + Drizzle ORM + better-auth, runs as a Cloudflare Worker
Web	`@repo/web`	9002	SvelteKit static SPA served by a Cloudflare Worker (static assets)

The API handles all business logic; the web app is a pure frontend that talks to the API via PUBLIC_API_URL.

Monorepo Layout

/
├── apps/
│   ├── api/          # Cloudflare Worker — auth, DB, Stripe, business logic
│   └── web/          # SvelteKit SPA — all UI and routing
├── packages/
│   ├── ui/           # Shared shadcn-svelte component library
│   ├── typescript-config/  # Shared tsconfig bases (svelte.json, worker.json)
│   └── eslint-config/      # Shared ESLint config
├── Justfile          # Convenience recipes (dev, build, deploy, db, lint)
├── turbo.json        # Turborepo task pipeline
└── pnpm-workspace.yaml

Package names use the @repo/* workspace alias.

Where Things Live

UI Components

Shared library: packages/ui/src/components/ui/ (shadcn-svelte / bits-ui)
- 56 components exported — read packages/ui/src/index.ts for the current list before building or installing anything
App-specific components: apps/web/src/lib/components/
Add new shadcn components: pnpm --filter @repo/ui ui:add <component-name>
Import alias: @repo/ui → packages/ui/src (configured in apps/web/svelte.config.js)
Styling: theme tokens only (bg-primary, text-muted-foreground, …) — no palette classes or color literals; see root AGENTS.md and the ui-and-theme skill

Auth

Server config: apps/api/src/auth.ts — better-auth v1 with Stripe plugin + emailOTP
Middleware: apps/api/src/middleware/auth.ts — resolves session, sets ctx vars
Helpers/access control: apps/api/src/helpers/access.ts
API routes: apps/api/src/routes/auth.ts
Client (web): apps/web/src/lib/authClient.ts
Form schemas: apps/web/src/lib/forms/ (login, register, password-reset, request-password-reset)

Database

Schema: apps/api/src/db/schema.ts — Drizzle ORM, SQLite (Cloudflare D1)
- Tables: user, session, account, verification, subscription, plan
DB instance: apps/api/src/db/database.ts (singleton, uses env.DB binding)
Drizzle config: apps/api/drizzle.config.ts
Migrations: apps/api/migrations/

Config Files

Cloudflare Workers: apps/api/wrangler.jsonc (D1 bindings, env vars, rate limits)
Web worker (static assets): apps/web/wrangler.jsonc
TypeScript: each app extends @repo/typescript-config/{svelte,worker}.json
Tailwind: v4 via @tailwindcss/vite plugin — no separate config file
Prettier: root .prettierrc (single quotes, print width 100, no trailing commas)
ESLint: packages/eslint-config/index.js — all apps inherit

Validators & Types

Zod form schemas: apps/web/src/lib/forms/*-schema.ts
- Pattern: export const [name]FormSchema = z.object({...})
API context types: apps/api/src/types.d.ts (AppBindings, AppVariables, AppEnv)
Auth types: AuthUser, AuthSession, ActiveSubscription from apps/api/src/helpers/access.ts
SvelteKit types: apps/web/src/app.d.ts
Web state: apps/web/src/lib/state/ (Svelte 5 state classes, e.g. settings.svelte.ts)

Available Commands

Root (runs all apps via Turbo):

pnpm dev        # Start all dev servers
pnpm build      # Build everything
pnpm lint       # Lint all packages
pnpm check      # Type-check all packages
pnpm format     # Prettier format everything

Just recipes (preferred for targeted work):

just dev-web / just dev-api / just dev   # Dev servers
just build-web / just build-api          # Builds
just deploy-web-staging / just deploy-web-production
just deploy-api-staging / just deploy-api-production
just db-push / just db-pull / just db-seed
just lint / just format / just check / just clean

API-specific:

pnpm --filter @repo/api cf-typegen       # Regenerate wrangler types
pnpm --filter @repo/api generate:db      # Generate Drizzle migration
pnpm --filter @repo/api migrate:local    # Apply migrations locally
pnpm --filter @repo/api test             # Run Vitest

Web-specific:

pnpm --filter @repo/web build:staging    # Build for staging env
pnpm --filter @repo/web deploy:staging   # Deploy the web worker to staging

Deployment (GitHub Actions — managed by Pinebase)

CI/CD lives in .github/workflows/deploy.yml:

Push to staging → quality gates (typecheck, format, lint) + build + deploy of the preview app. Push to main → same for the live app (main is only reached via Pinebase's promote flow — never push to it directly).
The pipeline decides on its own whether to deploy the api, the web app, or both, by comparing against the pinebase-deploy-staging / pinebase-deploy-production git tags (last deployed commit per environment). D1 migrations are applied automatically before an api deploy.
Never edit or delete .github/workflows/deploy.yml or the pinebase-deploy-* tags. apps/web/.env.staging and apps/web/.env.production are managed by Pinebase too (public URLs baked into the web build) — leave their Pinebase-written lines intact.

Conventions

Import aliases:

$lib/* — SvelteKit standard (apps/web/src/lib/)
@repo/ui — Shared component library
$env/static/public — SvelteKit public env vars (prefixed PUBLIC_*)

Naming:

Components: PascalCase.svelte (e.g. LoginForm.svelte)
Form schemas: camelCaseFormSchema (e.g. loginFormSchema)
API routes: lowercase kebab at /v1/* (e.g. /v1/subscriptions/access)
DB tables: lowercase singular (e.g. user, session, subscription)
Env vars: SCREAMING_SNAKE_CASE; public ones prefixed PUBLIC_
State classes: settings.svelte.ts (Svelte 5 reactive class pattern)

File organization:

API routes → apps/api/src/routes/<feature>.ts, registered in routes/index.ts
API middleware → apps/api/src/middleware/
API helpers → apps/api/src/helpers/
Web pages → apps/web/src/routes/ (SvelteKit file-based routing)

What to Inspect Before Editing

Area	Read first
Auth flows	`apps/api/src/auth.ts`, `middleware/auth.ts`, `helpers/access.ts`, `routes/auth.ts`
DB schema	`apps/api/src/db/schema.ts`, `drizzle.config.ts`, `migrations/`
Shared UI	`packages/ui/src/index.ts`, `packages/ui/src/components/ui/`
App-specific UI	`apps/web/src/lib/components/`, `apps/web/svelte.config.js`
API routes	`apps/api/src/routes/index.ts`, `src/types.d.ts`, `src/middleware/`
Web pages	`apps/web/src/routes/`, `src/lib/forms/`, `svelte.config.js`
Adding deps	Check root + app `package.json`; respect `.syncpackrc.json` for version sync
Build/deploy	`turbo.json` for task deps; `Justfile` for quick recipes