AGENT SKILL

express-expert

Use when implementing express functionality with production-grade patterns and safeguards.

使用场景后端与接口
License 许可
MIT
最近更新
2026-04-11
Stars
★ 3
Forks
0

01 前言 Front Matter

name
express-expert
metadata
{ "hermes": { "tags": [ "codex-agent", "backend-api" ], "source": "codex-field-kit/backend-api" } }
description
Use when implementing express functionality with production-grade patterns and safeguards.

03 SKILL.md 正文

Express Expert

Focus Areas

  • Middleware design and pipeline management
  • Route handling and parameter parsing
  • Error handling and custom error pages
  • Security best practices with Express
  • Middleware for logging and auditing requests
  • Static asset delivery and caching
  • Application configuration and environment management
  • Authentication and authorization mechanisms
  • Session management and cookie handling
  • Request validation and sanitation

Approach

  • Use a structured project layout for maintainability
  • Implement middleware for cross-cutting concerns
  • Utilize async/await for asynchronous operations
  • Centralize configuration with environment variables
  • Implement robust error handling middleware
  • Leverage Express Router for modular route management
  • Use Helmet for setting security headers
  • Optimize performance with compression and caching
  • Implement a logging strategy with Winston or Morgan
  • Keep dependencies up to date and minimal

Quality Checklist

  • Adherence to Express best practices
  • Routes are RESTful and consistent
  • All middleware are error-free and performant
  • Security headers are correctly set
  • Errors are handled gracefully and consistently
  • Logging provides necessary request and error details
  • Environment configuration is flexible and complete
  • Authentication and authorization are correctly implemented
  • No open vulnerabilities in dependencies or code
  • Code is clean and adheres to coding standards

Output

  • A structured Express application template
  • Middleware for common tasks and configurations
  • Comprehensive route examples with hierarchy
  • Examples of error handling practices
  • Static file serving and caching
  • Sample authentication and authorization flow
  • Example session management and cookie handling
  • Request validation and sanitation examples
  • Performance benchmark results for key routes
  • Documentation for application setup and usage

04 同仓库更多 Skills

0xharryriddle
0xharryriddle/codex-field-kit

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

前端开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

swarm-planner

[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

super-swarm-spark

Only to be triggered by explicit super-swarm-spark commands.

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

role-creator

Create and install Codex custom agent roles in ~/.codex/config.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).

★ 3
0xharryriddle
0xharryriddle/codex-field-kit

read-github

Read and search GitHub repository documentation via gitmcp.io MCP service. **WHEN TO USE:** - User provides a GitHub URL - User mentions a specific repo in owner/repo format - User asks "what does this repo do?", "read the docs for X repo", or similar - User wants to search code or docs within a repo

Skill与智能体开发
★ 3
0xharryriddle
0xharryriddle/codex-field-kit

planner

Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.

★ 3