「new」の検索結果

Research historical news events that moved (or are moving) an asset's price and plot them as data points directly on the chart. Click a marker in the Historic News tab to zoom the chart to that event and read the article. Useful for identifying the fundamental drivers behind price action — earnings, regulation, product launches, macro shocks, geopolitical events.

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

Create new skills with proper structure, compliance checks, and registration. Use when asked to create a skill, build a new skill, or scaffold a skill template. Enforces mk: prefix, sub-agents.md structure, and context engineering principles.

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

Practical UI refactoring and visual design review inspired by Refactoring UI by Steve Schoger and Adam Wathan. Use when an AI coding agent needs to improve an existing interface, audit visual polish, redesign a rough UI, review frontend code for hierarchy/spacing/typography/color/depth/image issues, or turn a plain implementation into a cleaner product-quality screen. Do not use for creating UI from scratch, scaffolding a new app, building a new landing page, or designing a new design system unless the user explicitly asks to review or refactor an existing interface.

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

Create a new dbt Silver model with SQL + YAML contract. Use when adding a new Silver layer model from a raw source table.

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

Use when invoked as $new-project or when creating a brand-new repository or project from scratch — scaffolds mise-pinned tools, a just task surface, the standard repo files, and CI for Python (uv), TypeScript (bun), Rust (cargo), or Go.

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

Creates a new Angular app using the Angular CLI. This skill should be used whenever a user wants to create a new Angular application and contains important guidelines for how to effectively create a modern Angular application.

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

Use when returning to a repo after a break, asking what changed, what's new for this stack, or invoking project-catch-up after explain-new-project. Scans the stack for important updates, deprecations, new helper tools, agent skills, and MCP servers online—plain-language brief saved as PROJECT_CATCH_UP.md.

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

Use when the user adds a project to the workspace, opens an unfamiliar repo, asks "what is this project", "explain this codebase", or invokes explain-new-project. Explores a newly opened workspace project and writes a plain-language report for a self-taught, non-technical user—quick start (what it is + how to run) first, then optional depth—and always saves PROJECT_GUIDE.md in the project root.

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

Plan, scaffold, implement, and integrate a complete new emulated computer or console in the EMULATORS repository. Use when Codex creates a new machine, platform, hardware model, or emulator executable; decides which existing CPUs, chips, memory, I/O, video, sound, ROM, and framework classes to reuse or extend; or coordinates several emulator subsystems into a bootable tested system.

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

Produce a weekly digest of what Ahmad saved in OpenMark over a given time window, clustered by topic. Use whenever Ahmad asks "what did I save this week", "what's new in OpenMark", "last week's saves", "this week's bookmarks", "what happened in my feed", "weekly recap", or any temporal summary of saved content. Faster than full newsletter — output is a scannable digest, not a published post. Triggers on "this week", "last week", "what's new", "weekly digest", "recent saves", "recap".

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

Compose a comparison newsletter from Ahmad's OpenMark saves — A vs B vs C, side-by-side, table-driven. Use when Ahmad wants to compare tools, models, frameworks, approaches, or platforms across his saves. Trigger phrases include "compare", "X vs Y", "head to head", "which should I use", "differences between", "trade-offs between", "/newsletter-comparison". Output centers a markdown table with consistent columns, supports it with short prose blocks, ends with a clear recommendation.

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

Bootstrap a new or existing project with a small, file-based documentation system so Claude Code keeps context, lessons, and decisions across session restarts instead of starting cold every time. Sets up a handful of markdown files under .claude/ (standing rules, a free-form note to your next session, a phased roadmap, a prioritized backlog, and searchable history/changelog archives) sized and split so the files read every session stay small while the archives grow without ever costing context. Use this whenever someone is starting a new project and asks how to structure it for long-running AI-assisted work, wants Claude to "remember" things between sessions without relying on chat history, asks for a CLAUDE.md + backlog + changelog setup, mentions "session continuity", "persistent context", "project memory system", or is retrofitting an existing codebase that has no such system yet. Also use to explain or extend an already-bootstrapped bottle system (add a rule, start the archival script, add a new backlog section).

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

Turns the text of a regulatory change (new regulation, amendment, rule, guidance or standard revision) into a DRAFT impact note: what changed against the prior text where supplied, who is affected as the text scopes it, an obligations table with dates and owners to confirm, and open interpretation questions for legal. States only what the text says; the rest is UNKNOWN. Use when the user asks to "brief legal on this new regulation", "list what we must do by when under this amendment", "compare the new standard with the version it replaces", "turn this directive into an obligations table" or "what does this rule mean for us". Do not use for assessing existing controls against a requirement set, use controls-gap-pack instead; for gapping a policy against a standard, use policy-gap-review. Drafts for human review; never approves, authorises or signs off.

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

Compares a changed HR policy with the version it replaces and drafts a clause-by-clause change log, a plain-language DRAFT employee briefing, a manager FAQ answered only from the policy text with clause references, and a list of open questions the people team must settle before release. Use when the user asks to explain, announce, summarise or brief a policy change, a new policy version or an updated handbook section, or says "what changed in the leave policy", "brief managers on the new handbook section" or "compare the old and new versions of this policy". Do not use for a single announcement with no version comparison, use announcement-drafter instead; for an FAQ from documents that are not a policy change, use faq-builder; for contract clauses, use clause-comparison-table. Drafts for human review; never approves, authorises or signs off.

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

Produces a DRAFT 30-60-90 day onboarding plan for a new hire from the role, the team context and the systems list: phase outcomes traced to the role, activities with a named owner and due window, an access and equipment request table, learning items, manager checkpoints and the items the manager must confirm. Use when the user asks to "build an onboarding plan for our new hire", "draft the induction plan for this role", "write a first 90 days plan", "put together a new starter plan with owners", "create a ramp plan from this job description" or "plan the integration of an internal mover". Do not use for writing the job description itself, use job-description-drafter instead; for interview questions or a scorecard, use interview-scorecard-builder. Drafts for human review; never approves, authorises or signs off.

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

Turn a supplied everyday photo into an original Chinese satirical newspaper poster, with photo-specific deadpan headlines, restrained editorial typography and a recognizable photographic scene. Use for 没什么大事日报, 生活小报, 宠物上报纸 or humorous photo newspaper requests.

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

End-to-end playbook for creating a new NV oOS Pro toolkit under addons/pro/includes/tools/<toolkit> — folder layout, service layer, tool class conventions (canonical envelope, two-gate sanitisation, capability flags), ALL seven registration surfaces (central registry, admin Tools section, settings status map, both WP-CLI commands, schedule presets, workflow presets, SA Toolkit Manager), fixture/oracle testing with a standalone smoke harness, and the phpcs gotcha checklist. Use when asked to build a new Pro toolkit, add a toolkit to the plugin, scaffold toolkit tools, register toolkit presets/toggles, or debug why a new toolkit's tools or presets don't appear. First case study: food-beverage (F&B Management, 21 tools, 2026-10-08, 20/20 Check-totals oracle verified). Complements mcp-ai-wpoos-toolkit-audit (hardening existing toolkits) and mcp-ai-wpoos-test-suite (repair).

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

Given the product and the existing page inventory, identify missing blog topics and generate new blog posts that capture search/AI intent using the query-fanout pattern. Use this skill whenever the user asks to "spawn blogs", "generate blog posts", "expand the blog", "build out a content cluster", "write blog ideas", "cover more search intents", "query fanout for blogs", or wants new long-form content that supports existing pillars. Output is one new post per topic in the project's existing post format (markdown, MDX, component, or CMS migration note), with frontmatter shape mirrored from an existing post.

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

Given the product offering and existing page inventory, create new core landing and resource pages (homepage refresh, features, solutions, pricing, comparison, resource hubs, about) that capture core product intent using the query-fanout pattern. Use this skill whenever the user asks to "spawn pages", "generate landing pages", "create marketing pages", "build a pricing page", "add a solutions page", "build out the site", "fill in missing pages", or wants new top-level marketing/product pages. Output is one new page per route in the project's native file format (component or markdown), matching the existing page style and framework idiom.

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

When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

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

Use when the user asks to "monetize my newsletter", "build a sponsorship rate card", or "model paid-subscription revenue"; produces a revenue model (paid tiers, ad/sponsorship inventory + CPM/flat rate card, referral/boost loops), a list-growth ↔ revenue projection, and honest-offer / disclosure checks for the SEND-D lever. Not for scoring the whole program or running D1 — use email-quality-auditor; not for the return math — use roi-calculator; not for the post-click page — use landing-optimizer. 邮件newsletter变现/赞助刊例/付费订阅测算

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

Comprehensive social media operations for B2B SaaS brand building and engagement. Use this skill to develop LinkedIn strategy, decide whether to run a LinkedIn newsletter and how to scope it, capture consented registrations from LinkedIn Events, check LinkedIn Live eligibility, manage Twitter/X presence, create YouTube content, engage on Reddit communities, build community, develop influencer and creator partnerships, vet a creator before paying them, start or fix a B2B podcast, book podcast guests and guest appearances, write show notes and transcripts, and execute organic social campaigns. Also triggers on: LinkedIn, LinkedIn newsletter, LinkedIn Events, LinkedIn Live, event registration form, subscribe to our newsletter on LinkedIn, marketing consent checkbox, Notify Employees, Twitter/X, YouTube, Reddit, community, influencer, creator partnerships, influencer vetting, engagement rate, fake followers, engagement pods, FTC disclosure, sponsored post disclosure, media kit, social media strategy, organic social, employee advocacy, podcast, podcast strategy, podcast guesting, show notes, audiogram, episode transcript.

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

Full-funnel paid advertising operations for B2B SaaS. Use this skill for PPC strategy, Google Ads optimization, LinkedIn Ads, social media advertising, programmatic buying, creative strategy, attribution modeling, budget allocation, budget pacing and planned-vs-delivered reconciliation, audience overlap and campaign self-competition audits, suppression lists, ROAS improvement, media spend optimization, and the media no auction sells — newsletter and podcast sponsorships, community and industry-publication placements, paid review-site listings on G2 and Capterra, and pay-per-lead content syndication. Also triggers on: PPC, Google Ads, LinkedIn Ads, social ads, programmatic, ad creative, attribution, media budget, paid campaigns, ROAS, CPA, ad spend, newsletter sponsorship, podcast sponsorship, community sponsorship, sponsor a newsletter, content syndication, pay-per-lead, cost per lead vendor, media kit, rate card, insertion order, direct buy, publisher partnership, make-good, G2 paid listing, Capterra ads, review site advertising, sponsorship ROI, budget pacing, we underspent our budget, are our campaigns competing with each other, audience overlap, self-competition, campaign cannibalization, suppression list, exclusion list, ad frequency across channels, how many ad accounts do we have.

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

Spawn a new Claude Code session with remote control enabled (default: a detached background session — via screen on macOS/Linux, via a minimized PowerShell Start-Process on Windows — fully remote-safe, no approvals/windows), so it appears in the mobile Claude Code session picker. Takes an optional directory path; defaults to the current working directory. Use when the user runs /rc-new.

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