ksmyl
- 7 skills
- 0 followers
- 6 hours ago last updated
- ▌ Nano Banana Pro · ksmyl bundleGenerate, edit, and iteratively refine images using Google Nano Banana Pro (Gemini 3 Pro Image). Use this skill whenever the user asks to create, generate, draw, design, or make any kind of image, photo, illustration, thumbnail, icon, logo, diagram, or visual asset. Also use when they want to edit, modify, touch up, or iterate on an existing image, or when they mention Nano Banana, Gemini image generation, or text-to-image. Even casual requests like "make me a picture of..." or "can you create a visual for..." should trigger this skill.
- ▌ Quality Cm Pm · ksmyl bundleHow to do QA, configuration management, and project management in ASPICE. Use this skill when performing quality assurance audits (SUP.1), managing configuration items and baselines (SUP.8), tracking problems (SUP.9), handling change requests (SUP.10), writing project plans (MAN.3), or defining measurements (MAN.6). Also use when you need to create Git baseline tags, write problem records (PR-xxx), write change requests (CR-xxx), understand QA independence requirements, or define project metrics. Consult this whenever you see SUP.1, SUP.8, SUP.9, SUP.10, MAN.3, MAN.6, or terms like 'baseline,' 'corrective action,' 'non-conformance,' or 'measurement strategy.'
- ▌ Doorstop Usage · ksmyl bundleHow to use Doorstop for requirements traceability in Agent V. Use this skill whenever you need to run Doorstop commands (create, add, link, publish, review), understand the document tree structure, create or edit YAML requirement items, fix Doorstop validation warnings, or understand parent-child relationships between documents. Also use when you see Doorstop prefixes like STR, SYSRS, SWRS, SWARCH, SWDD, UT, SWIT, SYIT, SWQT, SYQT, or when dealing with traceability links, suspect links, or review hashes.
- ▌ Architecture Design · ksmyl bundleHow to create ASPICE-compliant system and software architecture documents. Use this skill when designing system architecture (SYS.3), software architecture (SWE.2), or detailed design (SWE.3). Also use when allocating requirements to architectural elements, defining interfaces, describing dynamic behaviour with Mermaid diagrams, evaluating alternative architectures, defining resource consumption objectives, or creating Doorstop SYSARCH/SWARCH/SWDD traceability items. Consult this whenever you see WP 04-06 (system arch), WP 04-04 (SW arch), or WP 04-05 (detailed design).
- ▌ Aspice Fundamentals · ksmyl bundleASPICE 3.1 V-model reference for Agent V. Use this skill whenever you encounter ASPICE process IDs (SYS.1, SWE.2, SUP.8, etc.), base practice references (BP1, BP6), work product IDs (WP 17-12, WP 04-04), capability levels, traceability requirements, or any mention of the V-model. Also use when you need to understand what an ASPICE assessor expects, how processes relate to each other, or what 'assessment-ready' means. This is foundational context — consult it early in any Agent V task.
- ▌ Verification Testing · ksmyl bundleHow to write tests and verification evidence for ASPICE. Use this skill when creating unit tests (SWE.4), integration tests (SWE.5, SYS.4), or qualification tests (SWE.6, SYS.5). Also use when writing test plans (WP 08-52), test specifications (WP 08-50), recording test results (WP 13-50, WP 13-25), deriving tests from verification criteria (WP 17-50), creating Doorstop test spec items (UT, SWIT, SYIT, SWQT, SYQT), or when you need to understand what each test level verifies against. Consult this whenever you see 'verification,' 'qualification,' 'regression,' or 'test coverage' in an ASPICE context.
- ▌ Requirements Engineering · ksmyl bundleHow to write and manage ASPICE-compliant requirements. Use this skill when creating stakeholder requirements (STR), system requirements (SYSRS), or software requirements (SWRS). Also use when analyzing requirements for quality (atomicity, testability, ambiguity), establishing bidirectional traceability, writing verification criteria, performing consistency checks, or when you see references to SYS.1, SYS.2, SWE.1, or any requirement-related base practices (BP1-BP8). Especially important for the SWE.1.BP6 cross-link requirement between SWRS, SYSRS, and SYSARCH.