Menu
Development conventions and tooling for the telegramable monorepo. Use when working on code, dependencies, or builds.
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ê.
Baseado na classificação ocupacional SOC
Access Railway deployments, logs, and environment variables. Use when asked to check deployment status, view service logs, inspect or update environment variables, redeploy a service, or diagnose production issues on Railway.
Best practices for creating clean, atomic git commits with good messages. Use when: (1) staging and committing changes, (2) writing commit messages, (3) deciding what to group in a single commit, (4) handling pre-commit hook failures, (5) choosing between amend and new commit. Triggers on "commit", "stage", "git add", "write a commit message", or "commit my changes".
Spec-Driven Development methodology for AI-assisted development. Use when working with specs, planning features, multi-step changes, task breakdowns, design decisions, or any task involving a specs/ folder or .lean-spec/config.json.
Run multiple AI coding agent sessions in parallel using git worktrees — each agent isolated in its own worktree, working on a separate branch. Use this skill whenever the user wants to: run two or more AI agents simultaneously on different features or bugs, set up isolated agent workspaces in the same repo, push parallel branches to GitHub and open/update PRs, coordinate between concurrent agent sessions, or clean up after merging. Triggers on: "parallel agents", "multiple agent sessions", "git worktree", "run agents in parallel", "work on two things at once", "isolated agent workspace", "spin up another agent", or any request involving simultaneous AI-assisted development streams.
Spec-Driven Development methodology for AI-assisted development. Use when working with specs, planning features, creating/implementing/refining/organizing specs, checking progress, updating specs, task breakdowns, design decisions, or any task involving a specs/ folder or .lean-spec/config.json.
AI-native agent coordination model — defines abstract operations (spawn, fork, merge, observe, convergence, prune), coordination primitives (speculative swarm, context mesh, fractal decomposition, generative-adversarial, stigmergic), and composable playbooks for agent fleet orchestration. Use when designing multi-agent systems, composing coordination patterns, writing playbook configurations, validating runtime conformance, or any task involving agent fleet architecture. Also use when the user mentions agent swarms, agent fleets, coordination primitives, agent orchestration patterns, or multi-agent composition.
| name | development |
| description | Development conventions and tooling for the telegramable monorepo. Use when working on code, dependencies, or builds. |
| compatibility | Requires pnpm >=9.0 and Node.js >=22 |
| metadata | {"author":"telegramable","version":"0.1.0"} |
Standards and conventions for developing in the telegramable pnpm monorepo.
Activate this skill when:
telegramable/
├── apps/ # Deployable applications
│ └── web/ # @telegramable/web - Next.js frontend
├── packages/ # Shared libraries
│ └── ui/ # @telegramable/ui - UI components
├── src/ # Root package source (core runtime)
├── specs/ # LeanSpec specifications
└── tests/ # E2E and integration tests
All workspace packages use the @telegramable/ scope:
@telegramable/web - Web application@telegramable/ui - UI component library| Tool | Version | Purpose |
|---|---|---|
| Node.js | >=22 | Runtime |
| pnpm | >=9.15 | Package manager |
| TypeScript | ^5.x | Type checking |
# Install all dependencies
pnpm install
# Run root package in dev mode
pnpm dev
# Build root package
pnpm build
# Run E2E tests
pnpm test:e2e
# Run command in specific package
pnpm --filter @telegramable/web dev
pnpm --filter @telegramable/ui build
# Run command in all packages
pnpm -r build
# Add dependency to specific package
pnpm --filter @telegramable/web add <package>
# Add shared dependency to workspace root
pnpm add -w <package>
# Add dev dependency
pnpm add -D <package>
pnpm --filter @telegramable/web add -D <package>
workspace:* protocol for internal packagesTo use @telegramable/ui in @telegramable/web:
pnpm --filter @telegramable/web add @telegramable/ui
This creates a workspace:* reference in package.json.
mkdir apps/new-app
cd apps/new-app
pnpm init
Update package.json:
{
"name": "@telegramable/new-app",
"private": true
}
mkdir packages/new-lib
cd packages/new-lib
pnpm init
Update package.json:
{
"name": "@telegramable/new-lib"
}
After creating, run pnpm install from root to link the new package.
--filterpnpm ls -r to see workspace structurepnpm install --frozen-lockfile in CIThe GitHub Actions workflow uses:
--frozen-lockfile for reproducible buildsSee .github/workflows/copilot-setup-steps.yml for the setup configuration.