Comprehensive guidance for integrating Jupiter APIs (Ultra Swap, Lend, Perps, Trigger, Recurring, Tokens, Price, Portfolio, Prediction Markets, Send, Studio, Lock, Routing). Use for endpoint selection, integration flows, error handling, and production hardening.

Execute a strict Red-Green-Refactor TDD cycle for a single requirement at a time, in any language or framework. Use when the user provides a business rule, acceptance criterion, or feature requirement and wants a failing test written first, followed by minimum implementation, then a clean refactor. Works for unit tests, integration tests, UI component tests, and API tests across stacks including TypeScript, JavaScript, React, .NET (C#/xUnit/NUnit), Python, Java, and others. Triggered by phrases like "write a test first", "TDD", "red-green-refactor", "behavioral test", "test-driven", "failing test first", or "write the test before the code".

Execute a strict Red-Green-Refactor TDD cycle for a single requirement at a time, in any language or framework. Use when the user provides a business rule, acceptance criterion, or feature requirement and wants a failing test written first, followed by minimum implementation, then a clean refactor. Works for unit tests, integration tests, UI component tests, and API tests across stacks including TypeScript, JavaScript, React, .NET (C#/xUnit/NUnit), Python, Java, and others. Triggered by phrases like "write a test first", "TDD", "red-green-refactor", "behavioral test", "test-driven", "failing test first", or "write the test before the code".

Progressive concept teaching through three depth levels (Core → Mechanics → Deep Dive). Creates diagrams, provides annotated code walkthroughs from the current codebase, and builds explanations from fundamentals to production internals. Triggers: "teach me about [pattern/concept]", "how does [architecture/pattern] work", "walk me through [this implementation]", "tutorial on [concept]", "deep dive into [system/pattern]", "help me understand [this design]" Use when: user requests multi-level learning about code patterns, architecture, or implementation mechanics with checkpoint-based progression. Not for: quick answers, single-sentence explanations, code fixes, or "what does this line do" questions—those are standard assistance.

Extract actionable insights and valuable artifacts from web posts, articles, and technical documentation. Use when summarizing content, extracting key ideas from URLs/articles, preserving code snippets and diagrams, or creating visual summaries. Triggers on requests like "summarize this post", "extract insights from", "distill this article", "what are the key takeaways", or when a URL is shared for analysis.

Create tessl tiles containing docs, rules, or skills. Use when a user wants to create a tile, package content for tessl, or needs help with tile.json configuration. Also triggers on "create tile from", "convert to tile", "turn into tile", "make tile from", or "tile this repo" for existing content.

Fetches and validates current third-party API documentation, checks SDK version compatibility, and verifies correct method signatures and parameter shapes before writing or debugging integration code. Use when writing, editing, or refactoring code that calls any third-party SDK, API, or library method; debugging issues where an API call succeeds but the expected side-effect doesn't happen; installing or importing external packages; or when something 'doesn't work' and the code involves an external service.

Helps fix security vulnerabilities identified by DryRunSecurity. Activates when the user shares a DryRunSecurity comment (from a GitHub PR or GitLab MR) or asks for help fixing any security finding including SQL injection, XSS, CSRF, SSRF, path traversal, command injection, authentication bypass, authorization flaws, and prompt injection. Researches authoritative sources and applies fixes grounded in the user's specific codebase context.

Resolve pull request review comments by critically assessing each one, fixing source files (not generated files), regenerating derived artifacts, running lint/format, committing, pushing, and replying to comment threads. Use when the user asks to address PR feedback, respond to reviewer suggestions, fix issues from code review, or resolve GitHub review comments.

Create or update a CONSTITUTION.md that defines project governance — establishes coding standards, quality gates, TDD policy, review requirements, and non-negotiable development principles with versioned amendment tracking. Use when defining project rules, setting up coding standards, establishing quality gates, configuring TDD requirements, or creating non-negotiable development principles.

Create a feature specification from a natural language description — generates user stories with Given/When/Then scenarios, functional requirements (FR-XXX), success criteria, and a quality checklist. Use when starting a new feature, writing a PRD, defining user stories, capturing acceptance criteria, or documenting requirements for a product idea.

Generate a technical design document from a feature spec — selects frameworks, defines data models, produces API contracts, and creates a dependency-ordered implementation strategy. Use when planning how to build a feature, writing a technical design doc, choosing libraries, defining database schemas, or setting up Tessl tiles for runtime library knowledge.

Start a FastAPI dev server, verify docs and OpenAPI schema, test endpoints, and run pytest. Use when running, checking, or debugging a FastAPI application.

Scaffold a new FastAPI project with an opinionated directory layout, pydantic-settings config, and starter files. Use when creating a new FastAPI application from scratch.

Create tessl tiles containing docs, rules, or skills. Use when a user wants to create a tile, package content for tessl, or needs help with tile.json configuration. Also triggers on "create tile from", "convert to tile", "turn into tile", "make tile from", or "tile this repo" for existing content.

A simple hello world skill for testing publish workflows

Package a standalone skill into a Tessl tile for versioning, distribution, and evaluation. Creates tile manifest, validates directory structure, and ensures skill format compliance. Use when asked to "convert to tile", "package this skill", "create a tessl tile", "wrap skill in tile", or before running evals on a skill not yet in a tile.

Generate evaluation scenarios for Tessl tiles to measure skill effectiveness. Creates inventory of instructions from the skill, test cases with success criteria, and validates skill coverage. Use when asked to "generate evals", "create evaluation scenarios", "test this skill", "measure skill value", or "prepare for tessl publish".

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

Build UIs with Chakra UI components, layout primitives, and theming. Use when using Chakra UI, ChakraProvider, Box, Flex, Stack, or when the user mentions Chakra.

Implement Figma designs in code with accurate layout, spacing, typography, and tokens. Use when implementing designs from Figma, translating mockups to React/CSS, or when the user mentions Figma, design specs, or Dev Mode.

Apply Tailwind CSS utility-first styling, responsive design, and theming. Use when styling with Tailwind, building UI with utility classes, configuring tailwind.config, or when the user mentions Tailwind.

Implement real-time presence tracking with PubNub

A software security skill that integrates with Project CodeGuard to help AI coding agents write secure code and prevent common vulnerabilities. Use this skill when security concerns are mentioned, when reviewing code for vulnerabilities, or when implementing authentication, cryptography, or data handling.

Investigates a problem area in the codebase and finds or creates a tessl tile (rules, docs, skills) to teach agents how to handle it correctly. Use when agents keep making the same mistakes around a library, design pattern, or convention.

Run quality checks on Java code before committing. Validates against best practices, enterprise standards, and common issues. MUST be run before any git commit operation that includes Java files.