1,818 件 ・ 関連度順
概要と使いどころ
Maintain PlainTab runtime UI translations and i18n language packs. Use when adding, editing, formatting, validating, or reviewing UI text in js/i18n/*.js, js/languages.js, data-i18n markup, or t(key) calls; also use when onboarding/help copy or new settings need localized strings.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain HitKeep dashboard localization. Use whenever a contributor adds or changes user-visible dashboard text, Transloco keys, locale JSON files, OptimusUI locale behavior, language switching, translated labels, localized layout, date/number/duration formatting, or supported dashboard languages.
日本語の概要は準備中です。原文の説明を表示しています。
Tier vocabulary from a text or topic into everyday, academic, and technical categories with teaching priorities. Use when pre-teaching vocabulary or identifying language barriers in a text.
日本語の概要は準備中です。原文の説明を表示しています。
Modify a lesson plan using SIOP sheltered instruction principles to support language learners across all four skills. Use when planning lessons for classes that include EAL students.
日本語の概要は準備中です。原文の説明を表示しています。
Build students' capacity to read historical documents closely — attending to word choice, tone, and rhetoric as evidence of perspective. Use when students summarise sources without analysing language.
日本語の概要は準備中です。原文の説明を表示しています。
Retrieves translated patent claims from the Nexscope (Nexscope) patent database. Trigger when the user asks about patent claims, claims translation, viewing claims in specific languages (Chinese, English, or Japanese), querying patent claims by patent ID or publication number, analyzing claim text, claim translation, patent claim translation, Nexscope, patent translation. Also trigger when the user needs patent claim content in a specific language, even without explicitly mentioning translated claims.
日本語の概要は準備中です。原文の説明を表示しています。
Retrieve translated patent description (specification) text from Nexscope. Triggered when users request patent specification translation, patent full text in other languages, translated patent full text, or want to view patent specifications in Chinese, English, or Japanese, patent specification translation, patent description translation, Nexscope, or patent translation. Also triggered when users provide a patent ID or publication number and request specification/description content in another language, or mention "patent specification translation," "description translation," "translated full text," or similar intent.
日本語の概要は準備中です。原文の説明を表示しています。
Act as a project-management copilot (PM/PMO) for the delivery loop: charters, plans and schedules, estimates, risk registers, status reports, scope changes, stakeholder communication, meeting actions, lessons learned, and portfolio roll-ups, in a per-project `_project/` workspace. Use whenever the user wants to start, plan, track, rescue, or report on a project: "kick off this project", "make a project plan / timeline / WBS", "what date can I commit to", "build a risk register", "run a pre-mortem", "write the weekly status report", "the deadline slipped, what now", "turn this meeting into action items", "review my project portfolio", in any language ("quản lý dự án", "gestion de projet", "プロジェクト管理", "项目管理"), even when they never say "project management". Also use whenever a `_project/` directory exists and the user asks about schedule, deadline, risk, status, scope, budget, or stakeholders. Not for what to build (product-manager) or company-level bets (strategy-board).
Facilitate a full design-thinking engagement (Empathize, Define, Ideate, Prototype, Test) grounded in real user evidence. Use whenever the user wants to understand users deeply and design a solution for them: "run design thinking", "understand our users", "design user interviews", "synthesize these interview notes", "build personas", "write How-Might-We questions", "prototype this concept", "design a usability test", "our users are churning and we don't know why", in any language ("tư duy thiết kế", "nghiên cứu người dùng", "phỏng vấn khách hàng", "デザイン思考", "设计思维"), even when they never say "design thinking". Also use when the user drops raw interview notes, transcripts, or survey exports and wants insights, personas, or product decisions. Not for "is there a market for X" desk questions (market-researcher).
Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).
Analyze, draft, and review Insurance clauses for Construction contracts. Use when the user mentions insurance clause, coverage requirements, construction insurance, or asks to review, redline, or generate this clause type. Returns structured risk assessment, plain-language summary, and suggested alternative language.
日本語の概要は準備中です。原文の説明を表示しています。
Shape language across type, radius and icons carries brand personality. Use when starting a design system, picking icons or radius tokens, or reviewing visual consistency.
日本語の概要は準備中です。原文の説明を表示しています。
Translation and interpretation as language meta-skills -- equivalence theory (Nida's formal vs. dynamic equivalence), translation strategies (borrowing, calque, transposition, modulation, adaptation), interpretation modes (simultaneous, consecutive, sight), source text analysis, register preservation, cultural adaptation, untranslatability and compensatory strategies, machine translation literacy, and back-translation for verification. Covers literary, technical, legal, and community interpreting contexts. Use when translating between languages, evaluating translation quality, teaching translation skills, or understanding the limits of cross-linguistic transfer.
日本語の概要は準備中です。原文の説明を表示しています。
Grammar and syntactic structures across human languages -- word order typology (SVO, SOV, VSO, VOS, OVS, OSV), morphological systems (isolating, agglutinative, fusional, polysynthetic), agreement patterns (gender, number, case, person), phrase structure, clause embedding, and cross-linguistic universals. Covers constituent analysis, dependency vs. constituency grammars, grammatical relations (subject, object, oblique), ergativity vs. accusativity, tense-aspect-mood systems, and how grammar encodes meaning differently across language families. Use when analyzing sentence structure, comparing grammar systems, teaching grammatical concepts, or understanding why a learner makes transfer errors from their L1.
日本語の概要は準備中です。原文の説明を表示しています。
Computational thinking as a problem-solving discipline independent of programming languages. Covers the four pillars (decomposition, pattern recognition, abstraction, algorithm design), computational problem-solving methodology (understand, decompose, generalize, formalize, verify), abstraction levels (from hardware through user interface), modeling and simulation, automata and formal languages (DFA, NFA, regular expressions, context-free grammars, Turing machines), computational complexity classes (P, NP, NP-complete, undecidable), and constructionist pedagogy (learning by building, Logo, Scratch, physical computing). Use when approaching unfamiliar problems, teaching problem-solving strategies, analyzing problem complexity, or bridging between domain knowledge and computational solutions.
日本語の概要は準備中です。原文の説明を表示しています。
Deploys the current project to a live HTTPS URL via Cybrix. Activates on any request to make the current project public, get a URL for it, deploy it, ship it, host it, publish it, put it online, or make it live — including casual phrasings like "send this to the internet", "share this as a link", "give me a URL", "make this accessible online". Activates whether the user mentions Cybrix by name or not (when no other host like Vercel, Netlify, Cloudflare Pages, Railway, or Render is named). Also activates on equivalent phrases in other languages — Russian ("задеплой", "опубликуй", "выложи в сеть", "запушь это в инет", "сделай ссылку"), Spanish ("despliega esto", "publica esto", "ponlo en línea"), German ("deploy das mal", "stelle das online"), and other common languages where the intent is clearly to make a project publicly accessible via URL. Uses heuristic detection to determine if a project is static or needs a server runtime — works with any framework, not just a known list. Automatically detects and handles environment variables so the build receives everything it needs. Returns a live URL on *.cbrx.cc or a user-configured custom domain. Does NOT activate when the user explicitly names a different host (Vercel, Netlify, Cloudflare, Railway, Render).
日本語の概要は準備中です。原文の説明を表示しています。
Draft a new RFC document for the Incan language project. Use when the user asks to write, create, or draft an RFC, or wants to propose a new language feature or infrastructure change for Incan.
日本語の概要は準備中です。原文の説明を表示しています。
Show a nice greeting message with a timestamp. Use this when the user wants to greet or say hello, optionally to a certain subject <subject> and in a certain language <language>.
日本語の概要は準備中です。原文の説明を表示しています。
Guided codebase exploration for understanding a repo's architecture, patterns, and domain language before contributing. Not issue-specific. builds general understanding. Use when exploring a new repo, wanting to understand how a project works, or preparing to become a regular contributor. Not for learning a framework or language you have never used. Use oss-learn-stack for that.
日本語の概要は準備中です。原文の説明を表示しています。
Learn unfamiliar technologies used in a repo by studying how the repo actually uses them. Finds patterns, explains concepts in context, and points to examples in the codebase. Use when a repo uses frameworks, languages, or patterns you haven't worked with before. Not for mapping a repo's architecture or domain language. Use oss-explore-repo for that.
日本語の概要は準備中です。原文の説明を表示しています。
AgentQL is TinyFish's web automation and extraction toolkit that layers a natural-language query system on top of live sites. Its Python and JavaScript SDKs integrate with Playwright and let agents target data and interface elements without depending on brittle CSS selectors alone.
日本語の概要は準備中です。原文の説明を表示しています。
Use when navigating or refactoring code with a language server - choosing between semantic (LSP), exact-text (rg), and fuzzy/semantic search; anchoring LSP calls by position; gating degraded results; and disclosing tool substitutions, in any language.
日本語の概要は準備中です。原文の説明を表示しています。
Build or update a CONTEXT.md domain glossary for the current project. Establishes shared vocabulary with term definitions, avoid-aliases, and relationships so agents use consistent, concise language. This skill should be used when starting a new project, when domain terminology is inconsistent across sessions, when the user says "build a glossary", "define our terms", "shared vocabulary", or "domain language", or when an existing CONTEXT.md needs updating after new domain concepts emerge.
日本語の概要は準備中です。原文の説明を表示しています。
Extract transcript and key slides from a local video file, then create a vault-formatted lecture note. Use this skill whenever a user provides a local video file (.mp4, .mov, .mkv, .avi, .webm) and wants notes from it. Triggers on "lecture", "take notes", "I have a recording of", "class video", "transcribe this presentation", "process this video for notes", or /lecture. Works with any language — auto-detects transcript language.
日本語の概要は準備中です。原文の説明を表示しています。