Skip to content

notque/vexjoy-agent / skills/programming/programming

programming

Flagged

Language rules, workflows, and tooling: Go, Python, Rust, Kotlin, Swift, PHP, TypeScript type checks and debugging, OpenStack Python, MCP local-docs servers, Node.js backend APIs.

FileKindSize
SKILL.mdskill md19.3 KB
references/go/code-review.mdmarkdown12.0 KB
references/go/code-review/common-review-comments.mdmarkdown6.6 KB
references/go/concurrency.mdmarkdown11.5 KB
references/go/concurrency/concurrency-patterns.mdmarkdown5.7 KB
references/go/error-handling.mdmarkdown10.8 KB
references/go/error-handling/patterns.mdmarkdown4.2 KB
references/go/google-style-guide/SHA256SUMSother313 B
references/go/google-style-guide/UPSTREAM_REVISIONother41 B
references/go/google-style-guide/best-practices/part-01.mdmarkdown10.0 KB
references/go/google-style-guide/best-practices/part-02.mdmarkdown15.0 KB
references/go/google-style-guide/best-practices/part-03.mdmarkdown14.1 KB
references/go/google-style-guide/best-practices/part-04.mdmarkdown13.5 KB
references/go/google-style-guide/best-practices/part-05.mdmarkdown10.5 KB
references/go/google-style-guide/best-practices/part-06.mdmarkdown14.4 KB
references/go/google-style-guide/best-practices/part-07.mdmarkdown16.1 KB
references/go/google-style-guide/best-practices/part-08.mdmarkdown11.4 KB
references/go/google-style-guide/best-practices/part-09.mdmarkdown13.7 KB
references/go/google-style-guide/best-practices/part-10.mdmarkdown16.9 KB
references/go/google-style-guide/decisions/part-01.mdmarkdown15.0 KB
references/go/google-style-guide/decisions/part-02.mdmarkdown12.5 KB
references/go/google-style-guide/decisions/part-03.mdmarkdown11.5 KB
references/go/google-style-guide/decisions/part-04.mdmarkdown8.4 KB
references/go/google-style-guide/decisions/part-05.mdmarkdown9.8 KB
references/go/google-style-guide/decisions/part-06.mdmarkdown14.7 KB
references/go/google-style-guide/decisions/part-07.mdmarkdown13.3 KB
references/go/google-style-guide/decisions/part-08.mdmarkdown14.3 KB
references/go/google-style-guide/decisions/part-09.mdmarkdown15.3 KB
references/go/google-style-guide/decisions/part-10.mdmarkdown8.3 KB
references/go/google-style-guide/guide/part-01.mdmarkdown16.3 KB
references/go/google-style-guide/guide/part-02.mdmarkdown3.0 KB
references/go/google-style-guide/index.mdmarkdown8.4 KB
references/go/preferred-patterns.mdmarkdown12.5 KB
references/go/preferred-patterns/code-examples.mdmarkdown11.6 KB
references/go/quality-gate.mdmarkdown7.3 KB
references/go/quality-gate/common-lint-errors.jsonconfig7.6 KB
references/go/quality-gate/examples.mdmarkdown11.0 KB
references/go/quality-gate/makefile-targets.jsonconfig5.1 KB
references/go/sapcc-conventions.mdmarkdown34.6 KB
references/go/sapcc-conventions/api-design-detailed.mdmarkdown22.7 KB
references/go/sapcc-conventions/architecture-patterns.mdmarkdown18.6 KB
references/go/sapcc-conventions/build-ci-detailed.mdmarkdown18.7 KB
references/go/sapcc-conventions/error-handling-detailed.mdmarkdown20.1 KB
references/go/sapcc-conventions/extended-patterns.mdmarkdown7.1 KB
references/go/sapcc-conventions/go-bits-philosophy-detailed.mdmarkdown24.5 KB
references/go/sapcc-conventions/library-reference.mdmarkdown14.0 KB
references/go/sapcc-conventions/pr-mining-insights.mdmarkdown17.5 KB
references/go/sapcc-conventions/review-standards.mdmarkdown10.5 KB
references/go/sapcc-conventions/sapcc-code-patterns.mdmarkdown46.2 KB
references/go/testing.mdmarkdown9.7 KB
references/go/testing/go-benchmark-and-concurrency.mdmarkdown5.6 KB
references/go/testing/go-test-patterns.mdmarkdown9.0 KB
references/golang-general.mdmarkdown8.9 KB
references/golang-general/go-modern-code.mdmarkdown17.2 KB
references/golang-general/go-verification-workflow.mdmarkdown5.0 KB
references/golang-general/go-version-idioms.mdmarkdown6.8 KB
references/kotlin-general.mdmarkdown7.5 KB
references/kotlin-general/kotlin-patterns.mdmarkdown7.9 KB
references/kotlin-general/kotlin-security-testing.mdmarkdown4.4 KB
references/kotlin-general/kotlin-security.mdmarkdown11.1 KB
references/kotlin/concurrency-patterns.mdmarkdown5.4 KB
references/kotlin/kotlin-testing.mdmarkdown7.9 KB
references/mcp-local-docs.mdmarkdown6.9 KB
references/mcp-local-docs/mcp-patterns.mdmarkdown9.6 KB
references/mcp-local-docs/mcp-preferred-patterns.mdmarkdown6.9 KB
references/mcp-local-docs/server-templates.mdmarkdown4.4 KB
references/mcp-local-docs/typescript-async-patterns.mdmarkdown8.9 KB
references/nodejs-api.mdmarkdown7.3 KB
references/nodejs-api/auth-patterns.mdmarkdown10.0 KB
references/nodejs-api/middleware-patterns.mdmarkdown10.5 KB
references/nodejs-api/nodejs-security.mdmarkdown12.3 KB
references/nodejs-api/webhook-patterns.mdmarkdown9.9 KB
references/php-general.mdmarkdown4.7 KB
references/php-general/php-behaviors.mdmarkdown5.2 KB
references/php-general/php-conventions.mdmarkdown5.8 KB
references/php/modern-php-features.mdmarkdown4.4 KB
references/php/testing-patterns.mdmarkdown7.5 KB
references/python-general.mdmarkdown7.7 KB
references/python-general/flask-jinja-webapp.mdmarkdown5.7 KB
references/python-general/python-local-gates.mdmarkdown4.4 KB
references/python-general/python-modern-code.mdmarkdown23.1 KB
references/python-openstack.mdmarkdown5.2 KB
references/python-openstack/error-handling.mdmarkdown658 B
references/python-openstack/hacking-rules.mdmarkdown4.1 KB
references/python-openstack/openstack-patterns.mdmarkdown1.2 KB
references/python-openstack/oslo-patterns.mdmarkdown6.4 KB
references/python-openstack/output-format.mdmarkdown2.4 KB
references/python-openstack/preferred-patterns.mdmarkdown1.9 KB
references/python-openstack/rpc-versioning.mdmarkdown5.3 KB
references/rust-general.mdmarkdown8.2 KB
references/rust-general/rust-modern-code.mdmarkdown13.4 KB
references/rust-general/rust-verification-workflow.mdmarkdown5.5 KB
references/rust-general/rust-version-idioms.mdmarkdown7.0 KB
references/swift-general.mdmarkdown5.7 KB
references/swift-general/swift-patterns.mdmarkdown6.7 KB
references/swift-general/swift-security-testing.mdmarkdown6.6 KB
references/swift-general/swift-security.mdmarkdown13.3 KB
references/swift/preferred-patterns.mdmarkdown2.4 KB
references/swift/swift-testing.mdmarkdown6.6 KB
references/swift/task-patterns.mdmarkdown3.6 KB
references/typescript-debugging.mdmarkdown9.3 KB
references/typescript-debugging/debugging-workflows-async-memory.mdmarkdown5.8 KB
references/typescript-debugging/debugging-workflows.mdmarkdown5.6 KB
scripts/bench-compare.shscript7.1 KB
scripts/check-errors.shscript7.1 KB
scripts/check-interface-compliance.shscript6.4 KB
scripts/check-sapcc-auth-ordering.shscript5.5 KB
scripts/check-sapcc-httptest.shscript4.4 KB
scripts/check-sapcc-identify-endpoint.shscript5.8 KB
scripts/check-sapcc-json-strict.shscript4.9 KB
scripts/check-sapcc-time-now.shscript4.2 KB
scripts/check-sapcc-todo-format.shscript4.1 KB
scripts/gen-table-test.shscript4.2 KB
scripts/quality_checker.pyscript16.2 KB
scripts/sync-google-style-guide.pyscript2.5 KB
scripts/validate.pyscript6.3 KB

references/nodejs-api.md

View on GitHub
# Node.js backend APIs

Scope: Node.js server-side APIs: Next.js API routes, Express routers,
middleware, auth (JWT, OAuth, sessions, bcrypt), file uploads (validation,
S3/Cloudinary, Sharp), webhooks (signature verification, idempotency, retry),
email (SendGrid, Resend), payments (Stripe), background jobs (Bull, BullMQ,
node-cron), structured logging, Zod validation, security headers.

Not here: React/Next.js client code (`frontend` skill,
`references/typescript-frontend.md`); schema design, query tuning, migrations
(`data` skill, `references/database.md`); deployment, scaling, monitoring
(`kubernetes` skill); mobile native code.

Priorities, in order: security (validation, authn, authz, headers),
reliability (error handling, idempotency, retries, logging), performance
(efficient queries, caching, async), maintainability (clear errors,
structure, API docs).

## Hard rules (always apply)

- **Validate all input with Zod** before processing: body, params, and query.
  Treat all client data as untrusted.
- **Error-handling middleware**: try/catch with structured `ApiError`
  responses. Catch and format every error consistently.
- **JWT verification on protected routes**, with proper token validation and
  user context.
- **Security headers** (CORS, CSP, and the rest) on every API response.
- **Rate-limit public endpoints**: default 100 req/min per IP, stricter on
  auth endpoints (5 req/min). Use `express-rate-limit` or
  `upstash-ratelimit`.

## Defaults (on unless disabled)

- Structured logging with request IDs, user context, and error details.
- JSDoc on every public endpoint with request/response examples.
- Full stack traces in development only; sanitize in production.
- Explicit Zod schemas for body, params, and query.

## Optional (off unless asked)

- GraphQL schema generation: only when GraphQL is requested instead of REST.
- Microservices patterns (event bus, service mesh): only when distributed
  architecture is the focus.
- WebSockets: only for real-time features (chat, notifications, live updates).
- Migration scripts (Prisma, Drizzle, TypeORM): only when deploying schema
  changes.

## Verification stops

Mandatory, even when confident.

- After writing code: run the test suite and show the output.
- After claiming a fix: confirm it addresses the root cause; re-read the
  original error and confirm it can't recur.
- Before reporting done: run `npx tsc --noEmit` (if TypeScript) and the test
  suite; show the output.
- Before editing a file: read it first.
- Before committing: never commit to main; use a feature branch.

## Output shape

Before implementing, state: requirements, security considerations (auth,
validation, rate limits), external services (APIs, storage, email), and edge
cases to handle. During: show endpoint code, validation schemas, middleware,
test results. After: list what was completed and this checklist:

- [ ] Input validated with Zod
- [ ] Authentication required
- [ ] Rate limiting enabled
- [ ] Security headers configured

Pair with the `review` skill for code review of the result.

## Common errors

| Error | Cause | Fix |
|---|---|---|
| Validation failure | Input doesn't match the Zod schema (missing field, wrong type, bad format) | Return 422 with field errors: `safeParse`, collect all errors, format as `{field: [errors]}` |
| Authentication failure | Missing, invalid, expired, or malformed JWT / Authorization header | Return 401 with a clear message. Verify signature, expiry, structure. Implement a refresh flow for expired tokens |
| Rate limit exceeded | Client over the limit (default 100 req/min) | Return 429 with `Retry-After`. Sliding window or token bucket, keyed by IP or user ID, stored in Redis when distributed |

## Preferred patterns

- **Validate all user input.** Zod schemas, sanitize HTML, parameterized
  queries. Trusting `req.body` enables SQL injection, XSS, and logic errors.
- **Generic errors in production.** Log details server-side and use error
  tracking (Sentry). Sending `error.stack` to clients leaks paths, structure,
  and dependencies.
- **Rate-limit public endpoints.** Unlimited login, signup, and contact
  endpoints enable brute force, DoS, resource exhaustion, and spam.

## Rationalizations to reject

| Rationalization | Why it's wrong | Do this |
|---|---|---|
| "Input validation slows responses" | Validation prevents breaches | Always validate with Zod; cache schemas |
| "Authenticated endpoints don't need rate limits" | Authenticated users can still abuse APIs | Rate-limit all public endpoints |
| "We'll add security headers later" | Easy to forget; they prevent attacks | Configure CORS and CSP from the start |
| "Long JWT expiry is convenient" | Long tokens increase breach impact | 15-minute expiry plus refresh tokens |
| "Detailed errors help users" | Details leak system info | Generic messages in production; log details server-side |

## Hard gate patterns

Before writing API code, check for these. If found: stop, report, fix before
continuing.

| Pattern | Why blocked | Do instead |
|---|---|---|
| `req.body` without validation | Security hole | `const data = RequestSchema.parse(req.body)` |
| Plain-text passwords | Breach | `await bcrypt.hash(password, 10)` |
| Hardcoded secrets | Credential exposure | `process.env.SECRET_KEY` from env |
| SQL string concatenation | SQL injection | Parameterized queries or an ORM |
| Async without error handling | Unhandled rejections crash the server | try/catch or error middleware |

Detection:

```bash
# Unvalidated inputs
grep -r "req.body\|req.query\|req.params" src/ | grep -v "parse\|safeParse"

# Hardcoded secrets
grep -r "password.*=.*['\"]" src/ --include="*.ts" --include="*.js"

# SQL injection risks
grep -r "SELECT.*\${" src/ --include="*.ts"
```

Exception: internal service-to-service calls with shared types may skip
validation (still recommended).

## When to stop and ask

Resolve routine issues from repo evidence and existing authorization; record
assumptions and continue. Ask Jev when genuinely unsure. Rows marked
**(owner)** guard production, destructive, credential, public-exposure, or
persistence actions: get explicit owner confirmation first.

| Situation | Ask |
|---|---|
| Auth strategy unclear **(owner)** | "Use JWT tokens, sessions, or OAuth?" |
| File storage destination unknown | "Store files locally or in cloud (S3, Cloudinary)?" |
| Rate-limit requirements unclear | "What limits for public and auth endpoints?" |
| External service credentials needed **(owner)** | "Need API keys for [service]: where are they?" |
| Schema changes required | Load the `data` skill's `references/database.md` and plan the migration |

Decide explicitly before acting on: auth strategy (owner confirms), external
API keys (owner confirms), rate-limit values, production error-message content.

## Reference loading table

| When | Load |
|---|---|
| JWT auth, OAuth, password security, token refresh | [nodejs-api/auth-patterns.md](nodejs-api/auth-patterns.md) |
| Stripe/GitHub webhooks, signature verification, idempotency, queue offloading | [nodejs-api/webhook-patterns.md](nodejs-api/webhook-patterns.md) |
| Error middleware, Zod validation, rate limiting, CORS, security headers | [nodejs-api/middleware-patterns.md](nodejs-api/middleware-patterns.md) |
| Security, auth, injection, XSS, CSRF, SSRF, any vulnerability-related code | [nodejs-api/nodejs-security.md](nodejs-api/nodejs-security.md) |
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 197kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 197kUpdated Claude CodeCodexVerifiedInstall