本文へ移動
cccskills

「builds」の検索結果

1,202 件 ・ 関連度順

概要と使いどころ

Ships an app clone live on the user's own domain: a preflight gate (tests green, parity must-haves done, rebrand sweep clean, listing linted, legal pages up), production database and env vars, the host, DNS records for the domain and for email, Stripe live mode, OAuth redirects, monitoring, and mobile builds to TestFlight and Play. Use when the user says "deploy it", "ship it", "put it live", "connect my domain", "go to production", "publish the app", or after /replica-launch.

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

Jakeschincariol/replica-skill2,4502026年10月3日 更新

Rebuilds an app screen by screen from the recon map: app shell first, then the core flow as a vertical slice, then every screen with all its states, ticking off the feature matrix as it goes. Writes every line fresh, never the original's code, assets or copy. Use when the user says "build the clone", "build screen S07", "start building", "rebuild this screen", "implement the booking page", or after /replica-design.

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

Jakeschincariol/replica-skill2,4502026年10月3日 更新

Audit a directory of multilingual blog content for completeness, consistency, hreflang correctness, meta-tag parity, and freshness. Builds a translation coverage matrix, flags stale translations, validates hreflang and schema, and emits a prioritized report with runnable fix commands. Use when user says "locale audit", "blog locale-audit", "check translations", "multilingual audit", "translation check", "hreflang check", "Uebersetzungen pruefen".

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

AgriciDaniel/claude-blog2,3822026年10月9日 更新

Deploy a PortalJS portal to PortalJS Arc — Datopian-managed static hosting on Cloudflare. Builds a static export, uploads it, and returns a live SLUG.arc.portaljs.com URL. One command, one target. Use when a portal is ready to publish or redeploy to a live URL.

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

datopian/portaljs2,3622026年10月8日 更新

Dump Unity IL2CPP symbols from iOS/Android builds. Extract method names, addresses, and type info from IL2CPP binaries and global-metadata.dat, then generate IDA/Ghidra import scripts.

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

P4nda0s/reverse-skills2,2812026年5月6日 更新

crabbox

無料

Use Crabbox from macOS, Linux, or native Windows controllers to run OpenClaw Windows node builds, tests, and targeted proof on remote native Windows or WSL2 hosts, including Azure or brokered AWS leases and static SSH hosts. Use when remote Windows validation is needed or the user asks for Crabbox validation. Always report the actual provider, lease id, run URL, command, and result.

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

openclaw/openclaw-windows-node2,1492026年10月13日 更新

Builds questions and assessments that measure what they claim — matching item type to the thing being assessed, writing distractors that diagnose, and telling a question that measures learning from one that measures reading speed or test-taking. Use this to write or review assessment items, design a unit check or diagnostic, work out why scores do not match classroom performance, or decide how much evidence a claim about mastery actually needs.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.

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

cbrock84/headcount2,0512026年9月18日 更新

Produces design reference imagery before implementation — screen concepts, layout directions, and flows for web or mobile that make a verbal brief concrete enough to argue with. Use this when a brief needs visualizing before anyone builds, when comparing layout directions, when handing a developer a target, or when stakeholders are describing different things with the same words.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds and interrogates a project schedule — logic-driven sequencing, dependency types and lags, float and the critical path, resource loading and leveling, schedule risk analysis, and measuring progress against a baseline rather than against optimism. Use this to construct a schedule, audit one you have inherited, find out why a plan keeps slipping, work out what a date change actually costs, or judge whether a reported percentage complete means anything.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review cycle, or diagnose pay compression and equity issues.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows. Use this when starting a new interface, when screens have drifted apart visually, when the same component exists three times in slightly different forms, or when a token or component needs adding without breaking what exists.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on individual events, tuning out the noise that trains people to ignore alerts, and defining what happens when something fires. Use this to design or assess monitoring coverage, work out why an incident went unnoticed, cut alert volume without losing signal, or decide what a detection capability should cost.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.

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

cbrock84/headcount2,0512026年9月18日 更新

Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardize builds, roll out software or an OS upgrade, handle a lost device, or bring an unmanaged fleet under control.

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

cbrock84/headcount2,0512026年9月18日 更新

Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators. Use this to work out what applies to your business, stand up a compliance program, prepare for a regulatory exam or certification, respond to a finding, or assess exposure before entering a new market.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds reach through other people's audiences — co-marketing partnerships, creator and influencer programs, and community building. Use this to find and evaluate partners, structure a joint campaign or creator deal, plan a community strategy, or decide whether a partnership is worth the coordination cost.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked. Use this for annual or quarterly planning, when budget must be allocated or defended, when marketing activity feels busy but undirected, or when a plan needs pressure-testing before commitment.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone changing the dashboard.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help center, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and the sensitivities that show where a plan breaks. Use this to model a decision's financial consequence, build a forecast or long-range plan, evaluate an investment or hire, or pressure-test someone else's model before relying on it.

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

cbrock84/headcount2,0512026年9月18日 更新

Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dashboards proliferating. Use this to build a dashboard or report, design a metrics framework, set up self-serve analytics, decide what to measure, or diagnose why reporting exists but nobody uses it or trusts it.

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

cbrock84/headcount2,0512026年9月18日 更新

Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather than encouragement. Use this when an idea needs pressure-testing before anyone builds, when deciding whether something is worth pursuing, when assessing competition or willingness to pay, or when a validated idea needs a first-customers and MVP plan. Default to scrutiny; the useful answer is usually the unwelcome one.

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

cbrock84/headcount2,0512026年9月18日 更新