10x-lesson

Capture recurring patterns and rules into a dedicated document for future reference.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/lukasPWR/vartownik --skill 10x-lesson-lukaspwr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-lesson
Source: https://github.com/lukasPWR/vartownik/tree/main/.cursor/skills/10x-lesson
Command: npx skills add https://github.com/lukasPWR/vartownik --skill 10x-lesson-lukaspwr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps capture and document recurring patterns or rules, making them easily accessible for future reviews and implementations, improving consistency and efficiency in processes.

Core Features & Use Cases

  • Pattern Capture: Record a recurring rule or pattern into a dedicated document.
  • Future Reference: The captured patterns are referenced by various review and implementation skills.
  • Use Case: When encountering a design pitfall or bug pattern, use this Skill to document it and ensure it's considered in future reviews and implementations.

Quick Start

To record a new lesson, run the command: /10x-lesson "Feature flags should always have a kill date" --context "Feature Development" --problem "Features without kill dates lead to unused code" --rule "All feature flags must have a kill date" --applies-to "plan, implement, review"

Frequently Asked Questions about 10x-lesson

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document recurring software development patterns for future reference?

Documenting recurring patterns involves recording the context, problem, and rule into a dedicated lessons file. This ensures the pattern is consistently referenced during future reviews and implementations.

What is the best way to capture design pitfalls and bug patterns in software development?

The best way to capture design pitfalls is by logging the specific problem and its corresponding rule into a centralized document. This makes the pitfall easily accessible for future implementation and review processes.

How do I record a new rule for my development process?

You record a new rule by providing the context, the problem it solves, the rule itself, and applicable skills. The system then saves this structured information into a lessons document for future use.

Does pattern capture require specific input parameters to document a rule?

Yes, pattern capture requires specific user input parameters including context, problem description, the rule, and applicable skills. These inputs are necessary to properly document the pattern for future reference.

Can I use captured lessons to improve consistency in code reviews?

Captured lessons can be used to improve consistency in code reviews. The documented rules are explicitly referenced by various review and implementation skills to ensure past pitfalls are avoided.