Just1cup
- 8 skills
- 0 followers
- 5 hours ago last updated
- ▌ Secure API 2 · just1cup bundleEnforce security and performance best practices whenever Codex writes, reviews, or designs code that touches APIs as a client consuming external APIs (REST, WebSocket, GraphQL) or as a server exposing endpoints. Trigger on ANY of the following: - Writing API client code (fetch, reqwest, axios, httpx, or any HTTP lib) - Writing or reviewing API route/handler code - Integrating with external services (VirusTotal, AbuseIPDB, Shodan, Stripe, etc.) - Storing or transmitting API keys, tokens, or secrets - Designing request/response payloads, pagination, or caching strategies - Reviewing code that makes HTTP requests or exposes HTTP endpoints - Phrases: "call the API", "integrate with", "API key", "rate limit", "auth token", "fetch data from", "send request", "endpoint", "REST", "WebSocket", "cache the response", "retry logic", "timeout", "bearer token", "secret", "credentials" Apply to Rust, TypeScript/JavaScript, Python, Go, and shell scripts. When in doubt, apply.
- ▌ Secure API · just1cup bundleEnforce security and performance best practices whenever Claude is writing, reviewing, or designing code that touches APIs — as a client consuming external APIs (REST, WebSocket, GraphQL) or as a server exposing endpoints. Trigger on ANY of the following: - Writing API client code (fetch, reqwest, axios, httpx, or any HTTP lib) - Writing or reviewing API route/handler code - Integrating with external services (VirusTotal, AbuseIPDB, Shodan, Stripe, etc.) - Storing or transmitting API keys, tokens, or secrets - Designing request/response payloads, pagination, or caching strategies - Reviewing code that makes HTTP requests or exposes HTTP endpoints - Phrases: "call the API", "integrate with", "API key", "rate limit", "auth token", "fetch data from", "send request", "endpoint", "REST", "WebSocket", "cache the response", "retry logic", "timeout", "bearer token", "secret", "credentials" Apply to Rust, TypeScript/JavaScript, Python, Go, and shell scripts equally. When in doubt, apply — over-triggering is better tha
- ▌ Save Session Id · just1cup bundleSave the active Codex session ID before a conversation ends so the user can later resume. Use at the end of every Codex session, before final responses that finish, pause, hand off, or close work, and when asked to preserve or recover session continuity.
- ▌ Security Code Review · just1cup bundleUse this skill whenever the user wants to write code, security review, vulnerability analysis, or security audit of any code snippet, file, or codebase. Trigger on: "review my code for security issues", "check for vulnerabilities", "is this code secure?", "security audit", "find bugs/flaws in this code", "OWASP", "pen test this code", "is there an injection here?", "check for XSS/SQLi/SSRF/auth issues", or any request to analyze code with a security lens. Also trigger when the user pastes code and asks "what's wrong with this?" in a security context, or asks Codex to find security bugs before a deployment or code review. Apply even when the user doesn't say "security" explicitly but the context clearly involves hardening, authentication, authorization, input validation, or cryptography. When in doubt, apply this skill.
- ▌ Debugging Sistematico · just1cup bundleUse esta skill sempre que um bug, erro, comportamento inesperado, falha ou exceção for encontrado em qualquer aplicação — seja reportado pelo usuário, encontrado em logs, em testes, ou observado durante desenvolvimento. Aplique também quando o usuário pedir para "corrigir um bug", "investigar um erro", "consertar isso", "por que está falhando", ou similar. Esta skill impõe um processo obrigatório de 5 etapas (Reproduzir → Identificar Causa Raiz → Corrigir Causa Raiz → Testar com Testes Unitários → Validar os Testes) e proíbe pular direto para uma correção sem antes reproduzir e entender a causa raiz do problema. Não é uma skill de escrita de código genérica — é especificamente sobre o processo de diagnóstico e correção de bugs.
- ▌ Code Quality Principles · just1cup bundleUse this skill before implementing any feature, refactor, bug fix, code review, or code suggestion where maintainability, readability, simplicity, YAGNI, DRY, KISS, avoiding over-engineering, preventing speculative abstractions, reducing unnecessary dependencies, preserving existing architecture, or improving long-term code sustainability matters. Apply it to evaluate whether every code modification is necessary, appropriately deduplicated, simple, readable, and scoped to the current requirement.
- ▌ Secure Coding Knowledge Base · just1cup bundleUse this skill before implementing, modifying, reviewing, or suggesting code when the work should be grounded in official vendor documentation and secure coding guidance. It discovers the repository architecture and technologies, builds and reuses a persistent Reference Set of official documentation findings, and applies official docs, OWASP Top 10, OWASP ASVS, OWASP Proactive Controls, OWASP API Security Top 10, language best practices, framework best practices, vendor security guides, and secure-by-default principles. Trigger for code changes, architecture changes, dependency usage, authentication, authorization, cryptography, payments, API design, security reviews, hardening, validation, data handling, infrastructure, CI/CD, or any request where current official implementation guidance matters.
- ▌ Session Recovery Project Memory · just1cup bundleUse this skill at the beginning of a Codex session, and whenever the user asks to resume, continue, recover context, inspect previous sessions, restore a Codex conversation, initialize project memory, update project memory, or preserve architectural decisions and pending work across sessions. It detects the current repository, loads repository-local `.codex/` memory first, searches only relevant local Codex sessions for that repository, recommends the most recent session, supports user-selected session recovery, and updates persistent project memory files without mixing unrelated repositories.