「lia」の検索結果

Reliably extract text from PDFs using pdftotext when standard file reading fails.

日本語の概要は準備中です。原文の説明を表示しています。

Use run_shell with cd and heredoc syntax for complex Excel operations when read_file fails on XLSX or execute_code_sandbox fails on multi-step workbook creation

日本語の概要は準備中です。原文の説明を表示しています。

Use run_shell with inline Python as a reliable fallback when execute_code_sandbox or read_file fail

日本語の概要は準備中です。原文の説明を表示しています。

Reliable PDF generation using shell-based Python execution when sandbox fails

日本語の概要は準備中です。原文の説明を表示しています。

Use run_shell with python-docx as reliable fallback when read_file fails on .docx files

日本語の概要は準備中です。原文の説明を表示しています。

Search reusable OpenSpace skills locally, and browse cloud packages step by step when a cloud skill may help. Reusing proven skills saves tokens, improves reliability, and extends your capabilities beyond built-in tools.

日本語の概要は準備中です。原文の説明を表示しています。

Fallback workflow for reliable code execution when sandbox fails repeatedly

日本語の概要は準備中です。原文の説明を表示しています。

Reliable Python execution workflow when execute_code_sandbox or shell_agent fail

日本語の概要は準備中です。原文の説明を表示しています。

Extract text from DOCX files with shell-primary approach and Python zipfile fallback for maximum reliability

日本語の概要は準備中です。原文の説明を表示しています。

Fallback pattern for reliable file creation when code execution tools fail

日本語の概要は準備中です。原文の説明を表示しています。

Understand a codebase before looking for bugs in it - what each function assumes, what it guarantees, and what it depends on elsewhere. Use when starting an audit, threat model, or architecture review on unfamiliar code, and before any vulnerability-hunting pass.

日本語の概要は準備中です。原文の説明を表示しています。

Check code against the documentation that specifies it - which requirements hold, which the code contradicts, which are absent, and what the code does that no document mentions. Use when comparing an implementation against a whitepaper, protocol spec, or design document.

日本語の概要は準備中です。原文の説明を表示しています。

Prepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments). Use when preparing your own codebase to be audited by someone else, getting a repository review-ready before an external security review, deciding what to fix before auditors start, or asking what assessors need from a project. For understanding unfamiliar code you are about to audit, use audit-context-building instead.

日本語の概要は準備中です。原文の説明を表示しています。

Optimize CircleCI configuration for speed, reliability, and maintainability. Use when users ask to improve `.circleci/config.yml`, reduce CI runtime, tune caching/workspaces/parallelism, remove pipeline waste, or fix flaky pipeline behavior caused by configuration choices.

日本語の概要は準備中です。原文の説明を表示しています。

Turn raw PM content into a compliant, publish-ready skill. Use when creating or updating a repo skill without breaking standards.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose context stuffing vs. context engineering. Use when an AI workflow feels bloated, brittle, or hard to steer reliably.

日本語の概要は準備中です。原文の説明を表示しています。

Design a new PM skill through guided conversation. Use when you have raw content or an idea and want to shape it into a compliant skill.

日本語の概要は準備中です。原文の説明を表示しています。

Generate or analyze poetic paper-texture minimal zine posters with large negative space, a small editorial collage or focal element, experimental typography, and one clear color accent. Use when the user gives a theme, sentence, article, mood, object, photo, content brief, reference images, or an image folder and wants a final poster image, a production-ready image prompt, reusable style rules, or varied layouts that stay in one visual family.

日本語の概要は準備中です。原文の説明を表示しています。

Runs a six-phase research workflow from source bundle to publish-ready output. Use when researching an unfamiliar domain or compiling materials into one reference. Not for quick lookups or single-file reads.

日本語の概要は準備中です。原文の説明を表示しています。

Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible". Do NOT use for SEO (use seo), performance (use core-web-vitals), or comprehensive site audits covering multiple areas (use web-quality-audit).

日本語の概要は準備中です。原文の説明を表示しています。

Technology-agnostic guidance for modular systems: bounded contexts, clear boundaries, composability, state isolation, explicit contracts, failure containment, scaffolding workflows, split/merge criteria, sub-units inside a context, and compliance review signals. Use when designing or reviewing module structure, service boundaries, package layout, cross-cutting dependencies, "how should we split this?", modularity assessments, coupling between domains, greenfield context design, or architecture discussions without assuming a specific framework, language, or repository layout. Do NOT use for executing the full Patterns 1–5 repo decomposition pipeline or per-pattern inventories (use modular-decomposition), phased extraction roadmaps as the main deliverable (use decomposition-planning-roadmap), or end-to-end legacy migration strategy (use legacy-migration-planner).

日本語の概要は準備中です。原文の説明を表示しています。

Your pathfinder for navigating unknown codebases. Investigates with precision, implements surgically, and never assumes — if it doesn't know, it says so. Maintains a .notebook/ knowledge base that grows across sessions, turning every discovery into lasting intelligence. Summons available skills, MCPs, and docs when the mission demands. Use when fixing bugs, implementing features, refactoring, investigating flows, or any development task in unfamiliar territory. Triggers on "fix this", "implement this", "how does this work", "investigate this flow", "help me with this code". Do NOT use for greenfield scaffolding, CI/CD, or infrastructure provisioning.

日本語の概要は準備中です。原文の説明を表示しています。

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).

日本語の概要は準備中です。原文の説明を表示しています。

Reconcile bounded Stripe payment and payout records with supplied business records while preserving object IDs, currency, time zone, and discrepancy evidence.

日本語の概要は準備中です。原文の説明を表示しています。