By 0x4139
Pragmatic development toolkit — coding conventions, review agents, and workflow hooks that evolve through daily practice
API contract design, validation, and consistency between Go backends and TypeScript frontends. Use proactively when designing endpoints, reviewing API changes, or troubleshooting client-server mismatches.
System design, scalability analysis, and technical trade-offs. Use proactively when designing new features, evaluating architectural options, or assessing scalability.
PostgreSQL query optimization, schema design, RLS, and performance analysis. Use proactively when writing SQL, creating migrations, or troubleshooting database performance.
Systematic root-cause analysis for bugs, test failures, and unexpected behavior across Go and TypeScript. Use proactively when encountering errors, failing tests, or runtime issues.
Codemap generation, README updates, and documentation freshness checks. Use proactively when code structure changes and docs need to reflect the current state.
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
Turn a one-line objective into a step-by-step construction plan for multi-session, multi-agent engineering projects. Each step has a self-contained context brief so a fresh agent can execute it cold. Includes adversarial review gate, dependency graph, parallel step detection, anti-pattern catalog, and plan mutation protocol. TRIGGER when: user requests a plan, blueprint, or roadmap for a complex multi-PR task, or describes work that needs multiple sessions. DO NOT TRIGGER when: task is completable in a single PR or fewer than 3 tool calls, or user says "just do it".
Bun and TypeScript backend patterns for API routes, validation with Zod, caching, middleware, and database access. Use as reference when building Bun/TS APIs.
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Dev toolkit built through practice, not theory.
A Claude Code plugin — agents and skills for the full journey from writing code to shipping product.
claude plugin marketplace add 0x4139/praxis
claude plugin install praxis@0x4139
Or for local development:
claude --plugin-dir /path/to/praxis
Agents are specialized subprocesses that Claude dispatches autonomously — think of them as expert reviewers that activate when relevant. Skills are reusable knowledge that agents (or you) can invoke — conventions, patterns, and workflows captured as structured documents.
| Agent | Purpose |
|---|---|
api | API contract design, validation, and client-server consistency |
architecture | System design, scalability analysis, and technical trade-offs |
database | PostgreSQL optimization, schema design, RLS, and performance |
debug | Systematic root-cause analysis for bugs and test failures |
documentation | Codemap generation and documentation freshness checks |
frontend | Tailwind, component design, accessibility, and responsive patterns |
go | Idiomatic Go — concurrency, error handling, and performance |
infra | Kubernetes, Dockerfiles, CI/CD, and deployment configuration |
planning | Implementation planning for complex features and refactors |
security | Vulnerability detection, secrets scanning, and OWASP Top 10 |
tdd | Test-driven development with red-green-refactor enforcement |
typescript | Type safety, async correctness, and Node/web patterns |
writing | Technical and product writing — architecture docs, memos, plans |
| Skill | Type | Purpose |
|---|---|---|
go-standards | ref | Naming, formatting, linting configuration |
go-patterns | ref | Idiomatic patterns and conventions |
go-backend | ref | HTTP handlers, middleware, service layers, pgx |
go-testing | ref | Table-driven tests, benchmarks, fuzzing, TDD |
typescript-standards | ref | Naming, typing, ESLint, project structure |
bun-backend | ref | API routes, Zod validation, caching, middleware |
bun-runtime | ref | Bun as runtime, package manager, bundler, test runner |
frontend-patterns | ref | React, Next.js, state management, performance |
api-design | ref | REST conventions, pagination, error responses, versioning |
postgres-patterns | ref | Query optimization, indexing, schema design, RLS |
database-migrations | ref | Schema changes, zero-downtime deploys, sqlc |
docker-patterns | ref | Compose, multi-stage builds, networking, security |
design-system | ref | Design tokens, visual consistency, UI auditing |
conventional-commits | ref | Structured commit messages with SemVer correlation |
| Skill | Type | Purpose |
|---|---|---|
article-writing | cmd | Blog posts, guides, tutorials, newsletters |
social-content | cmd | X, LinkedIn, TikTok, YouTube, content repurposing |
market-research | cmd | Competitive analysis, TAM/SAM/SOM, fund diligence |
investor-materials | cmd | Pitch decks, memos, financial models |
investor-outreach | cmd | Cold emails, warm intros, follow-ups |
slides | ref | HTML presentations from scratch or PPT conversion |
blueprint | cmd | Project scaffolding and architecture blueprints |
ref = reference skill (loaded automatically by agents when relevant)
cmd = user-invocable skill (call directly via /praxis:skill-name)
make help # Show all targets
make validate # Lint all skill and agent frontmatter
make list # Show all agents and skills with descriptions
make install # Symlink for local testing
make release # Validate + bump version + tag + push
From Ancient Greek — πρᾶξις (prâxis). It means "action" or "practice," specifically the kind of doing where you learn by doing.
Aristotle distinguished three types of knowledge:
The key distinction from techne: techne produces an external product (a house, a sculpture). Praxis transforms the practitioner themselves. The goal isn't an artifact — it's becoming better at the thing through doing it.
This isn't a static template collection. It's a toolkit that evolves because you use it, notice what's missing, and refine it. The skills get better because you practice with them.
npx claudepluginhub 0x4139/praxis --plugin praxisCollection of backend development skills including Kysely SQL query conversion
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n<example>\nContext: Designing a new API\nuser: "We need an API for our social sharing feature"\nassistant: "I'll design a RESTful API with proper authentication and rate limiting. Let me use the backend-architect agent to create a scalable backend architecture."\n<commentary>\nAPI design requires careful consideration of security, scalability, and maintainability.\n</commentary>\n</example>\n\n<example>\nContext: Database design and optimization\nuser: "Our queries are getting slow as we scale"\nassistant: "Database performance is critical at scale. I'll use the backend-architect agent to optimize queries and implement proper indexing strategies."\n<commentary>\nDatabase optimization requires deep understanding of query patterns and indexing strategies.\n</commentary>\n</example>\n\n<example>\nContext: Implementing authentication system\nuser: "Add OAuth2 login with Google and GitHub"\nassistant: "I'll implement secure OAuth2 authentication. Let me use the backend-architect agent to ensure proper token handling and security measures."\n<commentary>\nAuthentication systems require careful security considerations and proper implementation.\n</commentary>\n</example>
Production-ready Claude Code configuration with role-based workflows (PM→Lead→Designer→Dev→QA), safety hooks, 44 commands, 19 skills, 8 agents, 43 rules, 30 hook scripts across 19 events, auto-learning pipeline, hook profiles, and multi-language coding standards
Expert agents for specific programming languages (Python, Go, Rust, etc.)
Verification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, an interactive setup wizard. Every skill has rationalizations + evidence requirements. Built for senior ICs and tech leads.
Efficient skill management system with progressive discovery — 410+ production-ready skills across 33+ domains