.Cursor

.Cursor from Texarkanine/ai-rizz.

by @texarkanine 15 skills

Skills in this plugin

15
  1. ▌
    Niko · texarkanine bundle
    Niko Memory Bank System - Niko Phase - Initialization & Entry Point
    0 repo stars
  2. ▌
    Niko QA · texarkanine
    Niko Memory Bank System - QA Phase - Post-Implementation Semantic Review
    0 repo stars
  3. ▌
    Nk Chat · texarkanine
    Load Niko's memory bank and begin a conversation
    0 repo stars
  4. ▌
    Nk Save · texarkanine
    Niko Memory Bank System - Mid-Phase Save & Commit
    0 repo stars
  5. ▌
    Niko Plan · texarkanine
    Niko Memory Bank System - Plan Phase - Implementation Planning
    0 repo stars
  6. ▌
    Shell Tdd · texarkanine
    Required test-driven development practice for writing shell scripts
    0 repo stars
  7. ▌
    Bash Style · texarkanine
    Required style guidelines for writing shell scripts where POSIX-compliance is not an explicit requirement
    0 repo stars
  8. ▌
    Niko Build · texarkanine
    Niko Memory Bank System - Build Phase - Code Implementation
    0 repo stars
  9. ▌
    Nk Refresh · texarkanine
    General-purpose guidance for taking a step back and getting un-stuck from a problem that you've tried to solve multiple times unsuccessfully.
    0 repo stars
  10. ▌
    Niko Archive · texarkanine
    Niko Memory Bank System - Archive Phase - Task Archiving & Cleanup
    0 repo stars
  11. ▌
    Niko Reflect · texarkanine
    Niko Memory Bank System - Reflect Phase - Post-Implementation Reflection
    0 repo stars
  12. ▌
    Niko Creative · texarkanine
    Niko Memory Bank System - Creative Phase - Design Exploration
    0 repo stars
  13. ▌
    Niko Preflight · texarkanine
    Niko Memory Bank System - Preflight Phase - Pre-Build Plan Validation
    0 repo stars
  14. ▌
    Shell Posix Style · texarkanine
    Required style guidelines for writing shell scripts where POSIX-compliance is REQUIRED
    0 repo stars
  15. ▌
    Illustrate Complexity · texarkanine
    Decide whether an explanation needs a diagram, pick the right Mermaid type, and write it so it renders. Use when explaining a system's structure, flow, or relationships - in docs, READMEs, design notes, prompts, plans, or a chat answer - even when nobody asked for a diagram. Not for charting numeric data.
    0 repo stars