「hr」の検索結果

Generate a single-file VR-style portfolio website — works are tiled on the inside of a 3D cylinder/sphere (concave wraparound, like an immersive headset), with mouse-controlled head tilt, long-press to drag and browse the infinite canvas, click to open work detail. Includes overlays for About / CV / Contact / Filter. Takes a natural-language description of the studio and works (images + brief copy); outputs ONE working .html file. Runs in BOTH Claude Code (writes to ~/Desktop) and GLM / online chat (outputs HTML inline). Trigger phrases: "做个 VR 作品集", "做个无限画布作品集", "做个穹顶包裹的作品集", "vr-canvas-gen ...", or when user drags this skill folder into chat asking for a wraparound/immersive portfolio site.

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

Chinese-first AI image-generation tool landing template — TwelveMei-style centered hero with floating icon-island nav, FlyFlowerSong serif display headline, textured pill CTAs, glass canvas mockup of the tool itself, monochrome ink palette. Built for Chinese creative-tool / generative-image / AI-工具 product pages aimed at designers and editors, not loud growth-marketing.

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

Step through versioning, tagging, and verification

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

Deliver a small bounded change inside an initialized SDD Composy workspace through the quick path: at most five implementation files, a registered TASK, TDD, evidence, trace, and a verified verdict, escalating otherwise. Use for a precise objective with no existing task — 'ajuste rápido via SDD', 'quick fix under SDD', 'small change to X in the SDD flow'. Do NOT use for an already registered task (sdd-execute), for architecture, migrations, or destructive work, or in repositories without SDD Composy (other plugins' quick).

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

Use when the user wants a new Product Requirements Document — 'criar um PRD', 'escrever os requisitos de', 'new PRD for', 'documento de requisitos' — through a 12-step interview, one question at a time, ending with an approval gate. Do NOT use to change an existing PRD (prd- refine) or to plan implementation.

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

Use when the user wants to change an existing PRD — 'refinar o PRD', 'adicionar requisito', 'atualizar escopo do PRD', 'update the PRD' — through targeted questions, bumping the version and re-opening approval. Do NOT use to create a PRD (prd-create).

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

Design bounded performance profiles with explicit load authorization, contextual samples, percentiles, and agreed thresholds.

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

Design isolated repeatable automation, distinguish interactive browser exploration, and handle flaky results through evidence and reproduction.

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

Delegate a bounded repository task to an allowlisted external coding CLI through the guarded Flow runner. Use for automatic provider selection or explicit Codex, OpenCode, Kimi, Gemini, or Kiro delegation that requires timeout handling and independent local review.

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

Deliver a small, bounded code change through inspection, a mini-plan, implementation, testing, review, and adversarial verification. Use for bug fixes, configuration changes, and features expected to touch no more than five files.

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

Use when an existing skill must be refactored to cut context and ambiguity without losing behavior, safety or fallbacks — 'refatorar a skill', 'reduzir esta SKILL.md', 'revisar skill com métricas' — with before/after metrics, preserved invariants and three review rounds.

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

Use when a change is small and already understood - at most three files, such as a typo, a config value, a rename, or a one-line bugfix - and a plan file would cost more than the change

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

Review a code diff or explicit file set through independent correctness and QA lenses. Use when the user asks for a code review, test-coverage assessment, pre-merge audit, or review gate in a PWDEV Flow workflow.

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

Discover and approve feature requirements through focused interviewing and repository research. Use when the user has a feature idea, unclear scope, conflicting requirements, or needs Flow context artifacts before design.

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

Transforma uma peça de conteúdo em várias — case em thread, webinar em posts, artigo em carrossel, vídeo em cortes. Use quando o usuário disser "reaproveitar", "transformar isso em", "adaptar para", "repurpose", "derivar conteúdo", "aproveitar melhor esse material", "do blog para as redes", ou apresentar material longo pedindo derivados. Produz peça nativa de cada canal, nunca copia e cola.

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

Escreve copy para redes sociais — post avulso, carrossel, thread e legenda — respeitando limite, formato e cultura de cada plataforma. Use quando o usuário disser "post para", "legenda", "conteúdo para LinkedIn", "carrossel", "social media", "adaptar para as redes", "texto do Instagram". Para o gancho isolado ver copy-hooks; para derivar de material existente ver copy-repurpose.

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

Automate browser testing, web scraping, and user workflow testing with Playwright across multiple browsers. Use when writing end-to-end tests for web applications, automating repetitive browser tasks, scraping data from websites, testing across Chrome/Firefox/Safari, taking screenshots for visual regression testing, testing authentication flows, filling and submitting forms programmatically, testing responsive designs across viewports, or any browser automation requiring reliable, cross-browser testing capabilities.

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

Improve code structure, readability, and maintainability without changing external behavior through systematic refactoring techniques like extracting functions, removing duplication, simplifying conditionals, and applying design patterns. Use when reducing technical debt, extracting functions or classes, removing code duplication, simplifying complex conditionals, renaming for clarity, applying design patterns, improving code organization, reducing coupling, increasing cohesion, or maintaining test coverage during structural improvements.

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

Implement real-time features using Convex reactive queries that automatically update when data changes, enabling live collaboration, instant updates, and reactive UIs without manual polling. Use when building live dashboards, implementing collaborative editing, creating chat applications, showing real-time notifications, building activity feeds, implementing presence indicators, creating reactive search, or any feature requiring instant data synchronization across clients.

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

Trace bugs backward through call stacks and execution flows to identify the original source of errors, invalid data, or incorrect behavior. Use when debugging complex issues, tracing error origins, investigating data corruption, following execution paths, identifying where invalid data enters the system, or finding root causes of cascading failures.

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

Apply systematic root cause analysis and debugging methodologies to diagnose and fix bugs, test failures, and unexpected behavior. Use when encountering production issues, investigating test failures, diagnosing performance problems, tracing error sources through call stacks, analyzing logs and stack traces, reproducing inconsistent bugs, debugging race conditions, investigating memory leaks, or applying scientific method to problem-solving before proposing fixes.

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

Facilitate ideation, explore alternatives, and refine concepts through structured brainstorming techniques before implementation. Use when starting new projects, designing features, exploring solutions, evaluating tradeoffs, challenging assumptions, generating creative ideas, planning architecture, or refining rough concepts into detailed designs.

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

Apply continuous improvement principles to iteratively enhance processes, code quality, team practices, and system performance through small, incremental changes. Use when improving development processes, optimizing workflows, reducing waste, enhancing code quality over time, implementing retrospective learnings, or fostering a culture of continuous improvement.

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

Optimize application performance through code splitting, lazy loading, caching strategies, bundle size reduction, render optimization, and profiling. Use when improving page load times, reducing bundle sizes, optimizing React rendering, implementing code splitting, configuring caching strategies, lazy loading components and routes, optimizing images and assets, profiling performance bottlenecks, implementing virtual scrolling for large lists, or improving Core Web Vitals and Lighthouse scores.

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