10x-lesson

Name: 10x-lesson
Availability: InStock
Author: Kryptonum

Capture recurring engineering rules by appending structured lesson entries to lessons.md.

1|Updated Feb 26, 2025

Search Tags:#quality gates #engineering workflow #append-only log #knowledge reuse #recurring rules #prompt interview

Ready to run

npx skills add https://github.com/kryptonum-dev/fabryka-atrakcji --skill 10x-lesson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: 10x-lesson
Source: https://github.com/kryptonum-dev/fabryka-atrakcji/tree/main/.agents/skills/10x-lesson
Command: npx skills add https://github.com/kryptonum-dev/fabryka-atrakcji --skill 10x-lesson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams proactively record recurring lessons so the same bug patterns and design pitfalls don’t keep getting rediscovered and re-litigated across future runs.

Core Features & Use Cases

Recurrence-focused capture: Records a lesson only when the rule would have changed framing or the fix on past work.
Structured rule entry: Collects Context, Problem, Rule, and Applies to, and appends a standardized entry for easy future scanning.
Append-only knowledge register: Creates the lessons file with a canonical header if missing, then appends one new entry per invocation.

Quick Start

Invoke /10x-lesson and answer the four prompts (Context, Problem, Rule, Applies to) so it appends a new recurring rule to context/foundation/lessons.md.

Frequently Asked Questions about 10x-lesson

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

FAQPage Schema

How do I record recurring engineering rules to prevent repeating the same mistakes?▼

You can record recurring engineering rules by appending a structured lesson entry into context/foundation/lessons.md. This captures the Context, Problem, Rule, and Applies-to fields for future lifecycle skills to reuse.

What is the best way to document design pitfalls so my team stops re-litigating resolved issues?▼

Documenting design pitfalls is best handled by an append-only knowledge register that adds standardized entries to a shared file. This ensures recurring rules are easily scannable and accessible for future runs.

How does a structured interview flow help capture recurring bug patterns?▼

A structured prompt interview captures recurring bug patterns by systematically collecting Context, Problem, Rule, and Applies-to fields. This structured rule entry ensures the captured knowledge changes future framing and fixes.

When should I append a new lesson to my engineering workflow knowledge base?▼

Append a new lesson when a repeated failure or design pitfall is recognized during framing, research, planning, or implementation work, and the captured rule is expected to change future engineering decisions.

Does the lessons file need to exist before capturing engineering rules?▼

No, the lessons file does not need to exist beforehand. The system performs append-only file creation with a canonical header if the file is missing, then appends one new entry per invocation.

Can I manually edit the lessons.md file after appending a recurring rule?▼

The system enforces an append-only log for knowledge reuse, creating the file with a canonical header if missing and appending one new entry per invocation. Manual edits outside this workflow are not part of the automated lifecycle.