Results for “llm implementation”

Reviews code for security vulnerabilities and guides secure implementation using OWASP Top 10:2025, ASVS 5.0, the OWASP Top 10 for LLM Applications (2026), and the OWASP Top 10 for Agentic Applications (2026). Use when reviewing code or a diff for security issues, implementing authentication, authorization, sessions, or cryptography, handling untrusted input, files, or URLs, hardening config, dependencies, or CI, or building LLM and AI agent features.

The English summary is being prepared. Showing the original description.

UE (user experience engineering) skill for defining end-to-end user experience behavior and interaction logic. Use for tasks like flow design, interaction models, state machines, error recovery, input validation, usability heuristics, accessibility, and turning UX intent into testable acceptance criteria for implementation.

The English summary is being prepared. Showing the original description.

Architecture-first UI/UX design skill for Codex that helps agents reason from product truth, user journeys, causal design decisions, art direction, interaction, responsive behavior, imagery, iconography, and motion before implementation, then validate the result through rendered browser critique.

The English summary is being prepared. Showing the original description.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

The English summary is being prepared. Showing the original description.

Dual-mode UX quality skill — runs a heuristic/accessibility/motion audit on the current codebase, or validates implementation against design mockups. Fixes all issues found and commits.

The English summary is being prepared. Showing the original description.

Translate a vague request or GitHub issue into a concrete, testable spec using five structured elements (problem, scope, acceptance criteria, edge cases, success criterion) before writing any code. Prevents scope creep, PR churn, and mid-implementation pivots.

The English summary is being prepared. Showing the original description.

Create QA checklists for verifying design implementation accuracy.

The English summary is being prepared. Showing the original description.

Transforms a rough idea into a detailed design document with implementation plan. Follows Prompt-Driven Development — iterative requirements clarification, research, design, and planning.

The English summary is being prepared. Showing the original description.

Provides reverse engineering techniques. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it when the vulnerability is already understood and the remaining task is exploitation; use pwn instead. Do not use it for pure web workflows, log or disk forensics, or standalone crypto problems unless reversing the implementation is the real blocker.

The English summary is being prepared. Showing the original description.

AI/ML Workflow Bundle workflow skill. Use this skill when the user needs AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

The English summary is being prepared. Showing the original description.

AI/ML Workflow Bundle workflow skill. Use this skill when the user needs AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

The English summary is being prepared. Showing the original description.

Use when comparing two or more code implementations against a spec or requirements doc. Triggers on "which repo is better", "compare these implementations", "evaluate both solutions", "rank these codebases", or "judge which approach wins". Also covers choosing between competing PRs or vendor submissions solving the same problem. Does NOT review a single codebase for quality — use code review skills instead. Does NOT evaluate strategy docs — use strategy-review. Requires a spec file and 2+ repo paths.

The English summary is being prepared. Showing the original description.

Map user journeys, onboarding paths, entry points, first actions, trust points, accessibility risks, and SEO/LLM handoffs for public websites without redesigning the visual system. Use this skill when the user asks how new readers, returning users, project reviewers, community members, buyers, or AI agents should move through a site and what each page must make clear before layout implementation.

The English summary is being prepared. Showing the original description.

Write a durable feature spec before touching code. Reads the codebase map, reads related models/migrations to ask technical questions (not generic ones), then produces a structured spec doc in docs/specs/. Designed to pipeline with /implementation --issue N. Use before any feature implementation.

The English summary is being prepared. Showing the original description.

Fast spec-driven implementation from a committed spec. Use after /spec to implement an issue with a phase roadmap, TDD waves, map patching, review, and pre-commit validation.

The English summary is being prepared. Showing the original description.

Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.

The English summary is being prepared. Showing the original description.

METAINFORMANT rules for directory src/metainformant/ml/llm. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.

The English summary is being prepared. Showing the original description.

METAINFORMANT rules for directory src/metainformant/ml/llm/ollama. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.

The English summary is being prepared. Showing the original description.

AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.

The English summary is being prepared. Showing the original description.

Build Retrieval-Augmented Generation (RAG) systems for LLM applications with vector databases and semantic search. Use when implementing knowledge-grounded AI, building document Q&A systems, or integrating LLMs with external knowledge bases.

The English summary is being prepared. Showing the original description.

Review US healthcare software for HIPAA privacy and security concerns. The skill guides checks on protected health information, vendor agreements, minimum necessary access, and audit records, while directing implementation and specialized review to related skills.

• Reviewing AI-generated visit summaries for HIPAA concerns
• Checking patient data flows into analytics services
• Planning minimum necessary access and audit records

Helps you use Unsloth for language model fine-tuning with LoRA and QLoRA, methods that adapt models with fewer trainable parameters. Supports API questions, implementation, and debugging using reference material drawn from official documentation.

• Learning how to fine-tune models with LoRA or QLoRA
• Looking up Unsloth features and APIs
• Investigating errors in training code

Build MCP servers, connectors that let AI models use external services through tools. This skill guides API research, tool design, implementation in TypeScript or Python, testing, and evaluation with realistic questions that require multiple tool calls.

• Connecting an external API to an AI agent
• Building an MCP server in TypeScript or Python
• Improving tool descriptions, inputs, and error messages

Analyze the last seven days of agent and model token usage to identify unnecessary spending. Recommend changes to model selection, prompt caching, and overlapping work, with estimated dollar savings, percentage reductions, and implementation priorities.

• Investigating higher-than-expected AI costs
• Matching model choices to task complexity
• Reviewing prompt caching efficiency