ruicore
- 30 skills
- 0 followers
- 4 hours ago last updated
- ▌ Tdd · ruicore bundleTest-driven development with vertical red-green-refactor cycles and behavior-preserving green-to-green refactor loops. Use when the user requests TDD, test-first feature or bug work, integration tests that drive implementation, or an internal restructure that must preserve observable behavior. Infer the contract from the request and repository evidence; ask only when unresolved material choices would change public or business behavior, data or security meaning, or scope.
- ▌ Diagnose · ruicore bundleEvidence-led diagnosis for hard bugs and performance regressions, using the full reproduce → minimise → hypothesise → instrument → test → fix → prevent loop when possible and a bounded, non-mutating assessment when reproduction is unsafe, unavailable, production-only, or outside the user's authority. Use when the user asks to diagnose or debug a failure or regression; do not broaden an assessment-only request into implementation.
- ▌ Genmedia · ruicore bundleUse the genmedia CLI to search, inspect, run, and manage 1200+ fal.ai model endpoints. Trigger when the user mentions "genmedia", "fal CLI", or asks to "search models", "run a model", "fetch schema", "check pricing", "upload to fal", "queue async job", "track request", or any direct interaction with the fal.ai endpoint catalog. This is the foundational skill. Every other fal.ai-related skill in this repo executes its work through genmedia commands. Use `--json` whenever the output will be parsed by an agent.
- ▌ Grill Me · ruicore bundleUse this skill when the user asks Codex to challenge, critique, review, pressure-test, or "grill" an idea, plan, architecture, implementation, PR, design doc, migration, rollout, or technical decision. Behave like a direct senior engineer reviewer focused on production realism, code-backed evidence, scope control, risks, trade-offs, and concrete next actions. Do not use it for simple factual questions, ordinary code explanation, or tasks where the user clearly wants direct implementation instead of critique.
- ▌ Paper MCP · ruicore bundleUse when editing an open Paper board through the local Paper MCP server at http://127.0.0.1:29979/mcp. Prefer this over Computer Use for Paper canvas reads/writes, image placement, HTML writes, node inspection, screenshots, and exports.
- ▌ Write A Prd · ruicore bundleUse this skill when the user wants to turn an idea, feature request, architecture proposal, product requirement, vague engineering request, design discussion, or rough implementation plan into a structured PRD or specification. Use it for writing PRDs, feature specs, requirements, acceptance criteria, scope boundaries, implementation-ready product briefs, or inputs that can later be converted into execution issues for Codex or engineering teams.
- ▌ Prd To Issues · ruicore bundleUse this skill when the user wants to convert a PRD, product spec, implementation brief, design doc, feature plan, or requirements document into structured execution issues. Use it for breaking work into vertical slices, defining dependencies, sequencing milestones, creating agent-ready tasks, identifying parallelizable work, and producing JSON issue plans suitable for Codex, GitHub issues, Linear, or harness-based execution systems.
- ▌ Radar Analysis · ruicore bundleAnalyze the multi-track ai-signal-radar repository to produce monthly or quarterly reviews, theme and trend synthesis, cross-period comparisons, or idea-mining reports from existing Ray-reviewed data. Use for historical analysis of an explicit systems or creation track, or an explicitly requested cross-track comparison, based on track-scoped data, radars, themes, generated indexes, and monthly reports without ingesting new weekly reports.
- ▌ Grill With Docs · ruicore bundleDeep, docs-grounded pressure-testing session for plans, domain models, workflow semantics, and architectural assumptions against repository language and implementation reality. Use when the user wants an adversarial, iterative grilling session rather than a one-shot architecture assessment. Default to read-only critique; update durable docs only with explicit user authority or an applicable repository rule requesting persistence. Route one-shot architecture assessments to architecture-review and settled-decision recording to decision-trace-writer.
- ▌ Buffer Publisher · ruicore bundleUse Buffer's GraphQL API to inspect Buffer accounts, organizations, channels, queues, posts, daily limits, and to create Buffer Ideas, drafts, scheduled posts, queued posts, or media posts. Use when the user asks to draft, schedule, queue, publish, edit, delete, review, list, or manage social posts through Buffer, or asks what is connected in their Buffer account.
- ▌ Ecosystem Review · ruicore bundleReview how a repository in any language actually uses its ecosystem technologies and their integration boundaries. Use for multi-language or polyglot library, framework, runtime, build, package, persistence, messaging, observability, testing, SDK, or platform integration reviews; infer languages automatically unless the user supplies them. Review-only by default; do not use for broad architecture, generic code style, security, performance, or every dependency.
- ▌ Medium Publisher · ruicore bundleDraft, format, and safely publish Medium stories through an authenticated browser. Use for Medium article preparation, editor formatting, draft creation, or publication; do not use for generic blog writing with no Medium delivery.
- ▌ Paper Deck Style · ruicore bundleMinimal, spacious, high-end slide design for Paper boards. Use when creating or extending presentations in Paper that should feel keynote-like: slightly off-white backgrounds, Apple-like typography, one strong idea per slide, real UI/diagram graphics instead of text-heavy explanation, soft muted accents, obvious visual flows, and subtle section style shifts.
- ▌ Linkedin Publisher · ruicore bundleDraft, format, attach media, save, verify, and safely publish LinkedIn posts through an authenticated browser. Use for LinkedIn post preparation, draft editing, media upload, publication, or troubleshooting the current Shadow DOM composer; do not use for generic social copy with no LinkedIn delivery.
- ▌ Architecture Review · ruicore bundleGeneral-purpose architecture review for any code repository. Use when Codex needs to assess concept ownership, authoritative sources, module boundaries, architecture decisions, architecture drift, duplicated concepts, scattered rules, hidden assumptions, over-engineering, architectural change surface, phased refactor planning, or how architecture exposes ownership and change boundaries to future coding agents. Do not use for ordinary code review, testing review, implementation review, framework review, style review, narrow bug diagnosis, or a standalone agent-legibility audit unless the user explicitly asks for architecture assessment.
- ▌ Excalidraw Diagrams · ruicore bundleCreate polished Excalidraw diagrams from text descriptions. Use when the user asks for a diagram, flowchart, architecture diagram, decision tree, process flow, data flow, system overview, or similar visual explanation, or says "draw this", "diagram this", "visualize this", or "make a chart". Produces styled `.excalidraw` files with consistent colors and can export a shareable excalidraw.com URL.
- ▌ Feishu Doc Archiver · ruicore bundleArchive Feishu Wiki or Docs pages and their linked documents locally, preserve offline images at the best available source quality, and consolidate verified duplicates when requested. Use for document downloads, blurry-image re-export, or keeping only high-quality archive images; not for cloud publishing or bug investigation.
- ▌ Readwise CLI Control · ruicore bundleUse when a user wants to search, export, organize, or automate Readwise or Reader data from Codex or another terminal agent, especially when browser auth should be avoided and an access token is available.
- ▌ Brand Deal Researcher · ruicore bundleFind paid promotion, sponsorship, brand deal, influencer campaign, creator partnership, affiliate, and paid collaboration opportunities in a user's Gmail or email exports; research each brand/client; dedupe follow-ups; prioritize fit; and produce a Markdown table, document, or spreadsheet of brand leads with notes. Use when the user asks to scan recent email for brand deals, paid promo offers, sponsorship pitches, creator partnerships, or to turn those leads into a table/spreadsheet/doc.
- ▌ Database Access Audit · ruicore bundleRead-only database access audit for batch operations, looped DB I/O, bulk writes, relation attach/detach, N+1, transactions, scope isolation, rowcount, concurrency, constraints, and indexes across any stack.
- ▌ Decision Trace Writer · ruicore bundleSecondary persistence workflow for durably recording a stable engineering decision, finding, or user-clarified constraint after the primary review, diagnosis, architecture, or implementation work establishes it. Use when the user or repository explicitly requests a decision trace, or when a settled decision should be preserved for future agents; do not use as the primary workflow for every review, diagnosis, or architecture task.
- ▌ Feishu Issue Debugger · ruicore bundleRead and investigate Feishu Project work items that report bugs or performance issues against local repositories, exact versions, screenshots, attachments, logs, and runtime evidence. Use when the user asks to analyze, reproduce, diagnose, or prepare a local fix for a bug work item in Feishu Project. Feishu access is always read-only; do not use for ordinary Feishu documents, non-bug work items, issue administration, issue mutation, or publishing.
- ▌ Python Backend Review · ruicore bundleReview Python backend repositories at the foundation layer for target Python version compatibility, Python implementation quality, type system clarity, async/sync correctness, exception semantics, configuration and environment handling, logging and observability, packaging and dependency hygiene, Python package hygiene, testing and maintainability, and Python complexity/readability. Use when Codex needs a version-aware Python backend fundamentals review against a user-specified or inferred Python version. Do not use for architecture review, deep agent-legibility review, framework-specific FastAPI, SQLAlchemy, Pydantic, or Django review, security audit, performance deep dive, onboarding review, or business-domain review unless the user explicitly asks to include those scopes.
- ▌ Weekly Radar Ingestion · ruicore bundleIngest Ray-reviewed systems or creation radar reports into the ai-signal-radar repository as durable signal records. Use when the user asks to ingest this weekly radar, add this reviewed report, import this week's signal report, store this AI radar, archive this reviewed report, or otherwise turn an approved AI signal report into radars/, data/, themes/, indexes/, and a commit.
- ▌ Agent Legibility Review · ruicore bundleFramework-agnostic repository review from the perspective of a future AI coding agent. Use when Codex needs to evaluate whether a repo is easy for agents to find, understand, modify, and safely evolve with minimal ambiguity; find discoverability problems, missing or duplicated authoritative locations, hidden conventions, cross-file invariants, ambiguous ownership, scattered change surfaces, unpredictable impact, and agent risk hotspots. This skill evaluates the agent interaction surface; use architecture-review to decide or redesign architectural ownership and boundaries. Do not use as an ordinary code-style, framework-specific, bug, performance, security, clean-code, maintainability, or generic architecture review unless the user explicitly asks for agent-legibility.
- ▌ Python Ecosystem Review · ruicore bundleReview how Python repositories use important ecosystem libraries and integration boundaries, automatically discovering concrete usage and evaluating it against version-appropriate practices. Use when Codex needs a Python review of framework, validation, ORM, migration, dependency injection, async, background job, HTTP client, testing, LLM/agent, observability, or runtime-library integration points. Review-only by default; do not use for broad architecture, generic Python style, full agent-legibility, security, performance, or framework-only reviews.
- ▌ Repository Layout Refactor · ruicore bundleRefactor a working repository from broad, weakly owned modules into concept-owned packages and localized change surfaces while preserving behavior. Use when large or flat modules contain multiple independent responsibilities, agents repeatedly edit the same hotspots, ownership is ambiguous, or the user asks to redesign and implement the source or test layout. Do not use for LOC-only cleanup, formatting, a narrow bug, a greenfield package layout, or a read-only architecture review.
- ▌ AI Career Signal Researcher · ruicore bundleUse when the user wants an AI Systems Engineering Signal Radar: researching AI systems engineering trends, AI infrastructure, agent infrastructure, production AI and LLM application engineering, agent/RAG/evals/MCP/workflow automation trends, YouTube/podcast/blog/GitHub/hiring-market signals, career skill demand for AI systems engineers, or Medium/LinkedIn/GitHub portfolio content opportunities. Optimized for a backend engineer with strong Python production experience transitioning into AI systems engineering and AI infrastructure engineering.
- ▌ Agentic Repository Execution · ruicore bundleCoordinate repository implementation through a master agent that discovers local rules, persists a scoped plan, delegates every production-file change to sub-agents, enforces authority boundaries, escalates material uncertainty, and closes evidence-based validation gates. Use when the user asks for delegated or multi-agent repository execution, a master/sub-agent workflow, staged autonomous implementation, parallel work with conflict control, or strict independent review of agent-written changes.
- ▌ Feishu Technical Doc Publisher · ruicore bundleTurn a local authoritative Markdown design or conclusion into a reader-ready Feishu technical document using the authenticated browser, including editorial restructuring, native blocks, diagrams, table layout, safe cloud editing, and publish verification. Use when the user asks to write, publish, or synchronize a local Markdown technical document to Feishu; do not use for ordinary Markdown editing without Feishu delivery.