Create Rule
Skill Verified ActiveUse when found gap or repetative issue, that produced by you or implemenataion agent. Esentially use it each time when you say "You absolutly right, I should have done it differently." -> need create rule for this issue so it not appears again.
To guide users in creating precise, actionable rules that enforce consistent agent behavior by clearly demonstrating correct patterns and contrasting them with common mistakes.
Features
- Methodology for creating agent rules
- Contrastive examples (Incorrect/Correct)
- Guidance on rule scope and structure
- Best practices for rule descriptions
- Iterative refinement process for rules
Use Cases
- When an agent repeatedly makes the same mistake
- To enforce project-specific conventions consistently
- To define clear boundaries for agent behavior
- When a specific code pattern needs to be standardized
Non-Goals
- Creating task-specific workflows (use a skill instead)
- Providing one-time instructions (use the prompt)
- Defining broad project context (use CLAUDE.md)
- Documenting multi-step procedures (use a skill)
Workflow
- Identify the behavioral gap
- Determine rule scope (global, path-scoped, user-level)
- Write contrastive examples (Incorrect/Correct)
- Write the rule description (WHAT and WHY)
- Assemble the rule file
- Validate the rule and iterate based on feedback
Practices
- Rule creation methodology
- Agent behavior enforcement
- Contrastive learning
Versioning
- info:Release ManagementThe repository has a recent commit but lacks explicit versioning information in frontmatter or release tags, and installation instructions reference 'main'.
Installation
First, add the marketplace
/plugin marketplace add NeoLabHQ/context-engineering-kit/plugin install customaize-agent@context-engineering-kitQuality Score
VerifiedTrust Signals
Similar Extensions
Coding Standards
100Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.
Moyu (摸鱼)
100과잉 엔지니어링 패턴이 감지되면 자동으로 활성화됩니다: (1) 사용자가 명시적으로 변경을 요청하지 않은 코드나 파일을 수정하는 경우 (2) 요청되지 않은 새로운 추상화 레이어(class, interface, factory, wrapper)를 생성하는 경우 (3) 요청되지 않은 주석, 문서, JSDoc, 타입 어노테이션을 추가하는 경우 (4) 요청되지 않은 새로운 의존성을 도입하는 경우 (5) 최소한의 편집 대신 파일 전체를 다시 작성하는 경우 (6) diff 범위가 사용자의 요청을 명백히 초과하는 경우 (7) 사용자가 "너무 많아", "거기는 건드리지 마", "X만 변경해", "간단하게", "그만" 등의 신호를 보내는 경우 (8) 발생할 수 없는 시나리오에 대한 에러 처리, 유효성 검사, 방어적 코드를 추가하는 경우 (9) 요청되지 않은 테스트, 설정 스캐폴딩, 문서를 생성하는 경우
CE Optimize
100Run metric-driven iterative optimization loops -- define a measurable goal, run parallel experiments, measure each against hard gates or LLM-as-judge scores, keep improvements, and converge on the best solution. Use when optimizing clustering quality, search relevance, build performance, prompt quality, or any measurable outcome that benefits from systematic experimentation.
Remember Interactive Programming
100A micro-prompt that reminds the agent that it is an interactive programmer. Works great in Clojure when Copilot has access to the REPL (probably via Backseat Driver). Will work with any system that has a live REPL that the agent can use. Adapt the prompt with any specific reminders in your workflow and/or workspace.
Neon Postgres
100Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
Sdk Dx
100Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: "SDK design", "developer experience", "API design", "SDK DX", "error messages", "type safety", "IDE integration", "SDK versioning", "migration guides", "client library design", "making SDKs feel native", "SDK best practices"