Search

PythonReactSEOPDF

lbds137 AI Skills

GitHub ↗

Browse published AI skills maintained by lbds137. Compare skill descriptions and follow each source repository for setup instructions.

Author statistics

Indexed skills

16

Repository stars across indexed skills

113

Repository forks

17

Average repository stars per indexed skill

7

Repository stars may repeat across skills from the same repository.

16 skills

Browse skills

GitHub

tzurot-caching

lbds137

Contains MANDATORY caching patterns for Tzurot v3. MUST be consulted before implementing cache layers or TTL strategies. Covers Redis patterns, cache-aside, and invalidation.

GitHub

tzurot-async-flow

lbds137

Contains MANDATORY BullMQ and async patterns for Tzurot v3. MUST be consulted before working with jobs, Discord deferrals, or retry logic. Covers queue architecture, idempotency, and error handling.

GitHub

tzurot-types

lbds137

Use when creating types, constants, Zod schemas, or working with data validation. Covers common-types package organization, runtime validation, and type guards across microservices.

GitHub

tzurot-council-mcp

lbds137

Best practices for using the Council MCP server in Tzurot v3 development - When to consult external AI, how to structure prompts, model selection, and multi-turn conversations. Use when planning major changes o...

GitHub

tzurot-db-vector

lbds137

Contains MANDATORY PostgreSQL and pgvector patterns for Tzurot v3. MUST be consulted before writing Prisma queries or migrations. Covers connection management, vector operations, and Railway-specific considerat...

GitHub

tzurot-git-workflow

lbds137

Contains MANDATORY git workflow rules for Tzurot v3. MUST be consulted before any git operation (commit, PR, rebase). Covers rebase-only strategy, commit format, and safety checks.

GitHub

tzurot-tooling

lbds137

Use when adding CLI commands, dev scripts, or tooling utilities. Covers the ops CLI structure, where scripts belong, and standardized commands for linting/testing.

GitHub

tzurot-docs

lbds137

Contains MANDATORY documentation procedures. MUST be consulted at session end or when updating CURRENT_WORK.md. Covers folder structure and knowledge continuity.

GitHub

tzurot-architecture

lbds137

Contains MANDATORY microservices architecture rules for Tzurot v3. MUST be consulted before creating new services or deciding where code belongs. Covers service boundaries, dependencies, and anti-patterns from...

GitHub

tzurot-code-quality

lbds137

Contains MANDATORY code quality rules enforced by CI. MUST be consulted before refactoring or when hitting ESLint limits. Covers complexity thresholds, extraction patterns, and rule suppression.

GitHub

tzurot-testing

lbds137

Contains MANDATORY Vitest testing patterns for Tzurot v3. MUST be consulted before creating any `.test.ts` file. Covers mock factories, fake timers, and promise rejection handling.

GitHub

tzurot-skills-guide

lbds137

Meta-skill for writing and maintaining Claude Code skills. Use when creating new skills, updating existing skills, or reviewing skill quality. Enforces progressive disclosure and size limits.

GitHub

tzurot-deployment

lbds137

Contains MANDATORY Railway deployment procedures for Tzurot v3. MUST be consulted before deploying, running migrations, or debugging production. Covers service management, log analysis, and health checks.

GitHub

tzurot-slash-command-ux

lbds137

Use when implementing Discord slash commands, building list/browse UX, adding buttons or pagination, or creating dashboard patterns. Covers standard naming, shared utilities, and confirmation flows.

GitHub

tzurot-security

lbds137

Security best practices for Tzurot v3 - Secret management, AI-specific security (prompt injection, PII scrubbing), Economic DoS prevention, Discord permission verification, microservices security, and supply ch...

GitHub

tzurot-observability

lbds137

Contains MANDATORY logging and debugging patterns for Tzurot v3. MUST be consulted before adding logs or debugging production. Covers structured logging, correlation IDs, and Railway log analysis.

The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.