「lean」の検索結果

Two-dimensional minimalist style with vibrant colors, clean typography, and no 3D effects for fast, user-friendly interfaces.

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

Contemporary editorial style with serif typography, minimal palettes, and clean layouts for polished digital products.

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

Straightforward, no-frills design with clean typography, neutral colors, and intuitive layouts that stay out of the way.

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

A clean, product-oriented default. Use when the brief doesn't call for a specific mood — good for B2B tools, dashboards, and utility pages. Content-first, chrome-second.

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

Team operations dashboard template — Linear/Asana-clean hybrid with sprint status hero, 4-segment progress bar, workstream cards, chronological activity stream with colored event badges, right-rail with today's schedule + team-presence + upcoming milestones. For team status snapshots, OKR reviews, "team this week" all-hands views.

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

Cozy cafe-inspired interface with warm tones, soft typography, and clean layouts for a relaxed browsing experience.

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

Simplicity-focused design with ample whitespace, legible typography, and a limited color palette to reduce visual clutter.

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

Publish the openrind-desktop-orchestrator npm package with clean git hygiene. Triggers when user mentions: - "openrind-desktop-orchestrator npm publish" - "publish openrind-desktop-orchestrator" - "bump openrind-desktop-orchestrator"

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

Review or refactor an existing SKILL.md and its bundled resources — a smaller always-loaded core, conditional references, preserved behavior, lean/guided consumer profiles, and an A/B protocol to compare a candidate with the previous version. Use when a skill repeats itself, loads references on every run, triggers too broadly or misses legitimate requests, or needs its efficiency measured across models. Do NOT use for writing a new skill from scratch, refactoring application code, translating a skill verbatim, or performing the target skill's own task.

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

Inventory, archive, and summarize PWDEV Flow project history safely. Use when the user asks to find stale artifacts, archive completed work, clean the Flow workspace without deletion, or generate a changelog from verified history.

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

Design precise, production-grade enterprise UI — dashboards, admin panels, SaaS interfaces, and data-heavy applications. Use this skill for professional software interfaces that need Jony Ive-level craft: clean, minimal, functional, with intentional personality. Do NOT use for creative landing pages, marketing sites, or experimental/artistic frontends.

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

Design clean, scalable, and maintainable REST and GraphQL APIs following industry best practices. Use when designing public or internal APIs, planning endpoint structures, defining request/response contracts, establishing versioning strategies, implementing authentication patterns, designing data models, creating API documentation, ensuring consistent error handling, optimizing for performance, or establishing service contracts between microservices.

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

Organize, categorize, rename, and manage files systematically using automated rules, naming conventions, and folder structures for efficient file management. Use when organizing uploaded files, implementing file naming conventions, categorizing files by type or metadata, creating folder structures, cleaning up messy directories, automating file movements, implementing media libraries, or building file management systems.

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

Three-axis orchestrator: (1) clean section boundaries — naming, routes, views, ViewModels, DB ownership, cross-section access; (2) internal cohesion — no EF in service layer, caching in service only, proper interfaces, reusable ViewComponents, architecture-test coverage; (3) focused tests — grouped under the section, covering invariants/negatives/triggers, pruned of redundancy. Push-and-bot-review loop. Use when a sizable PR landed, a section shows arch drift, or /pr-review returned a non-trivial violation list. Camps is the gold-standard reference.

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

Triage application logs, open GitHub issues, pending feedback, in-app Issues, and agent conversations. Runs five phases: logs → close shipped issues → feedback → in-app issues → agent FAQ gaps. Use when /whats shows pending feedback, checking app logs, cleaning up shipped issues, or working the in-app Issues backlog.

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

End-of-session cleanup for coding and project work. Use when the user says "finish", "wrap up", "done for now", or any variation of ending a work session.

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

Two-phase memory hygiene. Phase 1: scan external Claude Code memory (~/.claude/projects/<slug>/memory/) for durable rules to migrate into the repo and entries already duplicated by repo atoms. Phase 2: audit in-repo memory/, CLAUDE.md, docs/architecture/, and docs/sections/ for dead links, duplication, drift, and bloat.

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

Autonomous themed tech-debt cleanup. Reads docs/architecture/debt-ledger.yml, rotates to the least-recently-served debt theme, works it for a time budget (default 2h) or until drained, opens one PR, and asks judgment questions inline at the end. Use for daily debt burndown without Peter pointing at a target: grandfathered analyzer rules, architecture-test baselines, obsolete-field reads, cross-section stitching.

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

Stryker-driven test cull: delete slop, consolidate redundants, fill mutation-coverage gaps. Score up, test count and lines down. Use when the user says 'trim tests', '/trim-tests', or wants to clean up LLM-generated test bloat. No args picks the worst-scored file; argument scopes to a section, service, or file.

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

When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' or 'sharpen the messaging.' Use this when the user already has copy and wants it improved rather than rewritten from scratch. For writing new copy, see copywriting.

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

Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped. (gstack)

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

Scrape webpage content, extract metadata, download images, and prepare for import/migration to AEM Edge Delivery Services. Returns analysis JSON with paths, metadata, cleaned HTML, and local images.

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

Bulk-retouch a folder of portrait photos using Adobe tools — designed for wedding photographers and event photographers who need fast, walk-away batch processing. Use this skill when the user says "retouch my photos", "batch process these portraits", "process my wedding photos", "clean up this folder of images", "run my headshots through Adobe", or uploads/selects a folder of photos and wants them polished and ready to review. Automatically applies auto-straighten, auto-tone, and auto-light to every image. Outputs a preview grid and download folder. Access: 🔐 Signed-In required | Gen AI: ❌

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

Remove AI-generated code slop and clean up code style

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