[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71K13C6WG6TSW72MHWYAJCJ":3,"skill-same:01M71K13C6WG6TSW72MHWYAJCJ":66},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M71K13C6WG6TSW72MHWYAJCJ","guided-learning",null,"Trigger: explain this, explícamelo, no lo entiendo, profundicemos, enséñame, como junior, learning mode. Teach technical concepts progressively with repository-grounded examples, clear mental models, and concise visual diagrams.","Piioni\u002FNixie","Piioni","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121120380?v=4","01M71K0PBETCK9PA6X58C9ZWCX","Juan","01M71K0PC5ZM92QSRYJJRP9R3Q",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FPiioni\u002FNixie\u002Fblob\u002Fmain\u002Fhome\u002Fagents\u002Fskills\u002Fguided-learning\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"guided learning","learning","teach","concepts","clear","repository","models","concise","junior","with","examples","programming","explain","visual","technical","mode","trigger","diagrams","2026-11-10 10:12:30",false,"---\nname: guided-learning\ndescription: \"Trigger: explain this, explícamelo, no lo entiendo, profundicemos, enséñame, como junior, learning mode. Teach technical concepts progressively with repository-grounded examples, clear mental models, and concise visual diagrams.\"\nlicense: Apache-2.0\nmetadata:\n  author: gentleman-programming\n  version: \"1.0\"\n---\n\n## Activation Contract\n\nActivate for requests to understand architecture, code, tools, terminology, or unfamiliar project structure. Teach rather than merely answer. Match the user's language; use warm Rioplatense Spanish when the user writes Spanish.\n\n## Hard Rules\n\n- Explain concepts before implementation details; define every new technical term.\n- Start from what the user already knows and build one abstraction at a time.\n- Never invent repository behavior. Inspect relevant files before making code-specific claims.\n- Contrast new ideas with the user's known mental model when useful (for example, MVC).\n- Use the smallest useful visual: ASCII tree, call flow, Mermaid, or focused diff. Load `..\u002Fshow-me\u002FSKILL.md` when visual explanation applies.\n- Keep one lesson focused. Avoid jargon dumps, exhaustive option lists, and unexplained acronyms.\n- Separate verified facts, interpretation, and analogy.\n- Prefer one concrete repository example over several generic examples.\n\n## Decision Gates\n\n| Situation | Action |\n| --- | --- |\n| Codebase-specific question | Inspect code and cite paths\u002Fsymbols before explaining |\n| Concept is too broad | Split into a numbered learning sequence and teach the first step |\n| User is confused | Rephrase with a simpler model and a concrete example; do not repeat jargon |\n| User asks for implementation | Explain the design first, then propose the smallest change |\n\n## Execution Steps\n\n1. State the core idea in one sentence.\n2. Connect it to the user's existing knowledge.\n3. Show the smallest relevant diagram or flow.\n4. Map it to one or two real files when available.\n5. Explain why the boundary exists and what problem it prevents.\n6. Recap with a compact mental model and offer the next single lesson.\n\n## Output Contract\n\nReturn a concise explanation containing: core idea, visual model, concrete example, why it matters, recap, and the next recommended learning step. Do not claim mastery or completion without fresh evidence.\n\n## References\n\n- `..\u002Fshow-me\u002FSKILL.md` — visual explanation patterns.\n","## Activation Contract\n\nActivate for requests to understand architecture, code, tools, terminology, or unfamiliar project structure. Teach rather than merely answer. Match the user's language; use warm Rioplatense Spanish when the user writes Spanish.\n\n## Hard Rules\n\n- Explain concepts before implementation details; define every new technical term.\n- Start from what the user already knows and build one abstraction at a time.\n- Never invent repository behavior. Inspect relevant files before making code-specific claims.\n- Contrast new ideas with the user's known mental model when useful (for example, MVC).\n- Use the smallest useful visual: ASCII tree, call flow, Mermaid, or focused diff. Load `..\u002Fshow-me\u002FSKILL.md` when visual explanation applies.\n- Keep one lesson focused. Avoid jargon dumps, exhaustive option lists, and unexplained acronyms.\n- Separate verified facts, interpretation, and analogy.\n- Prefer one concrete repository example over several generic examples.\n\n## Decision Gates\n\n| Situation | Action |\n| --- | --- |\n| Codebase-specific question | Inspect code and cite paths\u002Fsymbols before explaining |\n| Concept is too broad | Split into a numbered learning sequence and teach the first step |\n| User is confused | Rephrase with a simpler model and a concrete example; do not repeat jargon |\n| User asks for implementation | Explain the design first, then propose the smallest change |\n\n## Execution Steps\n\n1. State the core idea in one sentence.\n2. Connect it to the user's existing knowledge.\n3. Show the smallest relevant diagram or flow.\n4. Map it to one or two real files when available.\n5. Explain why the boundary exists and what problem it prevents.\n6. Recap with a compact mental model and offer the next single lesson.\n\n## Output Contract\n\nReturn a concise explanation containing: core idea, visual model, concrete example, why it matters, recap, and the next recommended learning step. Do not claim mastery or completion without fresh evidence.\n\n## References\n\n- `..\u002Fshow-me\u002FSKILL.md` — visual explanation patterns.\n",{"name":5,"license":15,"metadata":42,"description":7},{"author":43,"version":44},"gentleman-programming","1.0","main","db0489c64ee7ca811664d3e1451edb815c233897","home\u002Fagents\u002Fskills\u002Fguided-learning","https:\u002F\u002Fgithub.com\u002FPiioni\u002FNixie","https:\u002F\u002Fgithub.com\u002FPiioni","Software Developer at Sipay | Sipos Payments & POS Integrations :milky_way: ","2026-10-05 15:17:02",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add Piioni\u002FNixie --skill guided-learning",{"tool":58,"command":59},"bunx","bunx skills add Piioni\u002FNixie --skill guided-learning",{"tool":61,"command":62},"pnpm","pnpm dlx skills add Piioni\u002FNixie --skill guided-learning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPiioni\u002FNixie\u002Fblob\u002Fmain\u002Fhome\u002Fagents\u002Fskills\u002Fguided-learning\u002FSKILL.md",true,[],[67,85,103,121,129,149],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":37},"01M71K15S1V5QEYPKM45Z3XD95","show-me","Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.","MIT","https:\u002F\u002Fgithub.com\u002FPiioni\u002FNixie\u002Fblob\u002Fmain\u002Fhome\u002Fagents\u002Fskills\u002Fshow-me\u002FSKILL.md",[],[75,76,77,28,36,26,78,79,80,81,82,83,84],"show me","show","me","help","shape","understand","artifacts","code","html","user",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":37},"01M71K11ZS6ZECRHM5DE4VE54A","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002FPiioni\u002FNixie\u002Fblob\u002Fmain\u002Fhome\u002Fagents\u002Fskills\u002Fgrilling\u002FSKILL.md",[],[87,92,93,94,35,95,96,97,98,99,100,101,84,102],"stress-test","when","decision","about","grill","plan","thinking","test","use","stress","idea",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":37},"01M71K10PHRXD39GSD9HXXQ9DA","grill-with-docs","A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.","https:\u002F\u002Fgithub.com\u002FPiioni\u002FNixie\u002Fblob\u002Fmain\u002Fhome\u002Fagents\u002Fskills\u002Fgrill-with-docs\u002FSKILL.md",[],[110,111,96,28,112,113,114,115,116,117,97,118,119,120],"grill with docs","docs","sharpen","glossary","go","design","true","which","interview","as","adr",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":37},"01M71K0ZC6VQMVXXH35Q88WPPS","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002FPiioni\u002FNixie\u002Fblob\u002Fmain\u002Fhome\u002Fagents\u002Fskills\u002Fgrill-me\u002FSKILL.md",[],[128,96,77,118,97,116,115,112],"grill me",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":71,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":37},"01M71K0X89FYRQC1PY68N3019R","domain-modeling","Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.","https:\u002F\u002Fgithub.com\u002FPiioni\u002FNixie\u002Fblob\u002Fmain\u002Fhome\u002Fagents\u002Fskills\u002Fdomain-modeling\u002FSKILL.md",[],[136,137,138,139,140,120,141,142,143,144,100,93,112,145,146,147,148],"modeling","domain modeling","domain","context","recording","model","project","editing","writing","terminology","build","domain model","codebase",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":37},"01M71K0V1VTR2YB0E1VH7A0ZFD","pi-customization","Trigger: pi customization, customize pi, configurar pi, personalizar pi, mejorar pi, Pi APIs, Pi settings, Pi extensions. Configure and improve Pi using only official Pi documentation and APIs.","https:\u002F\u002Fgithub.com\u002FPiioni\u002FNixie\u002Fblob\u002Fmain\u002Fhome\u002Fagents\u002Fpi-agent-config\u002Fskills\u002Fpi-customization\u002FSKILL.md",[],[156,157,158,35,159,160,161,162,30,163,164,165,166,167],"pi customization","customization","pi","official","settings","documentation","customize","extensions","configure","pi extensions","only","improve"]