context-engineering
Context engineering patterns for AI-assisted development. Use when optimizing prompts, managing context windows, structuring CLAUDE.md files, creating skills/commands, or improving AI code generation quality. Triggers on context, prompt engineering, AI workflow, or skill creation keywords.
- License 许可
- MIT
- 最近更新
- 2026-05-18
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- context-engineering
- description
- Context engineering patterns for AI-assisted development. Use when optimizing prompts, managing context windows, structuring CLAUDE.md files, creating skills/commands, or improving AI code generation quality. Triggers on context, prompt engineering, AI workflow, or skill creation keywords.
03 SKILL.md 正文
Context Engineering for Claude Code
CLAUDE.md Best Practices
- Keep under 500 lines — dense, factual, no fluff
- Structure: What → Stack → Commands → Rules → Patterns
- Include ACTUAL file paths, not descriptions
- List critical env vars
- Document tech debt (file + line count)
- Update after every major change
Skill Structure
.claude/skills/[skill-name]/
SKILL.md — Main skill file with YAML frontmatter
scripts/ — Helper scripts
templates/ — Output templates
examples/ — Reference examples
- YAML frontmatter:
name,description(trigger conditions) - Description must include trigger keywords
- Keep actionable — Claude should know WHAT to do, not just theory
- Include Aurion-specific adaptations
Command Structure
.claude/commands/[namespace]/[command].md
# Title— Clear action name## Instructions— Numbered steps$ARGUMENTS— Dynamic parameter from user- Steps must be concrete and executable
- Reference actual project paths and tools
Context Window Optimization
- Front-load critical information
- Use links to files instead of embedding large content
- Structured data > prose (tables, lists, code blocks)
- Remove redundant information
- Prioritize: Rules > Patterns > Examples > Theory
Multi-Agent Patterns (from Ruflo)
- Task Decomposition: Break complex tasks into atomic subtasks
- Specialist Routing: Route subtasks to specialized agents
- Result Aggregation: Combine agent outputs into coherent result
- Feedback Loops: Verify outputs and iterate if needed
- Memory: Store learnings for future tasks
Prompt Patterns for Code Generation
- Specify the EXACT output format (file path, code structure)
- Include constraints upfront (TypeScript strict, no any, no comments)
- Reference existing patterns in the codebase
- Request validation steps (typecheck, build, test)
- Use "Think step by step" for complex architectural decisions
Anti-Patterns
- Don't dump entire files into context — reference by path
- Don't repeat information already in CLAUDE.md
- Don't create skills for one-time operations
- Don't over-engineer prompt structure
- Don't add unused commands that clutter the namespace
04 同仓库更多 Skills
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
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.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".