Skip to main content
rule CX Codex

market — Claude Code rule: market research and installation

This rule routes market research through the last30days engine, from query checks to a saved brief. It applies to trend scans, competitor research, and market discovery.

MIT ★ 1,472 updated 2026-11-05

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent
Open on GitHub

What market does

Every research task starts with oma market detect-trap. If the check rejects a query, the agent must show the user a reframed version; bypassing it requires --force and renewed explicit consent. The rule resolves the last30days engine and calls it through oma market run rather than building a separate collection or clustering pipeline.

On each run, the agent reads the engine’s SKILL.md and follows its workflow, including query planning and output requirements. If the engine is missing, Python 3.12+ is unavailable, or execution fails, the task stops. A WebSearch-only summary does not count as market research under this rule. Projects without Python 3.12+ cannot complete the engine run.

The brief goes to .agents/results/market/{topic-slug}-{YYYYMMDD}.md; raw engine files go to market.save_dir, whose default is .agents/results/market/raw/. First-run setup, credential storage, and a Python install managed by uv require user approval. Queries targeting private individuals’ personal data are rejected before the engine starts.

What it helps with

  • screen a research query for traps before collecting results
  • run market research through the last30days engine
  • build SWOT or PESTEL sections from engine output clusters
  • save a research brief and raw engine files to configured paths

Example prompts for the agent

  • Research trends around local AI editors and save a market brief.
  • Compare task-planning competitors and add a SWOT based on the resulting clusters.
  • Check this market research query and suggest a reframe if it fails the initial screen.

How to install market

1Plugin marketplace

/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent

2Manually: put the files in place

.claude/rules/market.md

The paths frontmatter field limits the files

Step by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use

Questions about market

How do I install market in Claude Code?

Run /plugin marketplace add first-fluke/oh-my-agent, then /plugin install oma@oh-my-agent. The rule file is .claude/rules/market.md.

What does the market rule do?

It sets the checks and workflow for research through the last30days engine, along with the brief’s format and location. A summary based only on WebSearch violates the rule.

What does market need to run?

The last30days engine and Python 3.12+ are required. Sources that need keys are enabled through the engine’s setup wizard with user consent.

Source text

market.md · MIT
---
description: Market research standards - trap detection, installed last30days engine, framework layer, LAW enforcement
globs:
alwaysApply: false
---

# Market Research Standards

## Core Rules

1. **Preflight first**: every market research task starts with `oma market detect-trap`. If it refuses, surface the reframe to the user — never bypass without `--force` and explicit user reconfirmation.
2. **One engine, installed as a skill**: research runs on the upstream `last30days` engine through `oma market run`. `oma market resolve` finds the copy installed through the skills CLI (or a `market.path` / `LAST30DAYS_HOME` pin); `oma market update` installs it when missing (`bunx skills add mvanhorn/last30days-skill --skill last30days -g -y`) and otherwise updates it. Install only after the user agrees. Do not hand-roll harvesting, scoring, or clustering.
3. **Follow the upstream contract**: read the resolved engine's `SKILL.md` (`engine.skillMd`) top to bottom every run and follow it — setup wizard, pre-research resolution, query plan, PRECONDITION GATE, OUTPUT CONTRACT. The only substitutions are skipping its Python-hunt block and replacing the raw `python3 scripts/last30days.py` call with `oma market run` (same arguments).
4. **Never WebSearch-only**: if the engine cannot run (no engine, no Python 3.12+, non-zero exit), stop and report; a WebSearch-only synthesis presented as market research is a contract violation.
5. **Keyless-first**: Reddit, HN, GitHub, Polymarket, arXiv, Techmeme, Digg, and web run without keys. Keyed sources (X, TikTok, Instagram, YouTube transcripts, …) are enabled only through the upstream setup wizard with user consent; skipped sources stay visible in the footer.
6. **Frameworks cite the engine**: SWOT / Porter's 5F / PESTEL sections use only clusters present in the engine output, cited as `[name](url)`; plain text when a URL is missing, never `[name]()`. Auto-toggle: pain/trend → SWOT; competitor → SWOT + 5F; discovery → SWOT + PESTEL; `--frameworks` overrides.
7. **LAW enforcement**: the engine's badge is the first line; upstream LAWs 1–8 plus `resources/output-laws.md` self-check must pass before the file is written.
8. **Single brief, single date**: `.agents/results/market/{topic-slug}-{YYYYMMDD}.md`; raw engine files under `market.save_dir` (default `.agents/results/market/raw/`). Same-day rerun overwrites.
9. **Personal data refuse**: refuse queries that target a private individual's personal data before running the engine. Founders, creators, and public handles are allowed (upstream person mode).
10. **Side effects are consented**: first-run `.env` creation, credential storage, and a `uv`-managed Python install happen only after the user says yes in the upstream Step 0 flow.

© First Fluke · MIT · first-fluke/oh-my-agent

Similar IDE rules

Everything for Marketing and content →
competitor-teardown 101-skills competitor-teardown — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode that runs structured competitive analysis. Produces feature matrices, SWOT tables, pricing comparisons, and positioning maps. CX Codex +1 65,800installs competitive-intelligence-analyst davila7 competitive-intelligence-analyst — a Claude Code subagent for competitor analysis and market research. It pulls data from public sources, runs SWOT and Porter's Five Forces, and writes structured reports to files. CX Codex 1,561installs competitor-analysis aj-geddes competitor-analysis — a skill that walks the agent through competitor research: direct and indirect players, a comparison matrix, SWOT, and a findings report. Useful before pricing or positioning calls. CX Codex +1 610installs competitive-analysis OrchestKit competitive-analysis generates Porter's Five Forces models, SWOT grids, competitor dossiers, and positioning maps. Runs when researching market viability or crafting sales battlecards. CX Codex +1 125installs market-scan Paweł Huryn market-scan — a command for strategic analysis of competitive landscape. Runs SWOT, PESTLE, Porter's Five Forces, and Ansoff Matrix together and delivers a unified report with cross-framework synthesis. CX Codex +1 ★ 28,211repo stars pm-market-research Paweł Huryn pm-market-research is a Claude Code plugin for studying users and markets through feedback, segmentation, personas, and competitor analysis. Its commands cover feedback analysis, competitor comparisons, and user research. ★ 28,211repo stars

From the same set69

The whole set →
qa-reviewer qa-reviewer — a code review agent that scans for OWASP vulnerabilities, performance bottlenecks, accessibility gaps and code quality issues. Runs before you merge and flags each finding with severity and remediation. CX Codex ★ 1,472repo stars mobile-engineer mobile-engineer implements mobile features across Flutter, React Native, Swift, and Kotlin following Clean Architecture boundaries. CX Codex ★ 1,472repo stars backend-engineer backend-engineer is a Claude Code subagent for API, authentication, and database migration tasks. It joins work on those tasks when requested. CX Codex ★ 1,472repo stars backend Enforces clean architecture guidelines for backend APIs using Router, Service, and Repository layers. Keeps business logic out of HTTP routes. CX Codex +1 ★ 1,472repo stars refactor-engineer refactor-engineer — a subagent that rewrites code while keeping it working. Identifies hot spots, wraps them with safety tests, and applies one atomic transformation at a time. CX Codex ★ 1,472repo stars pm-planner pm-planner is a subagent for Claude Code and Codex that breaks down requirements, creates API contracts, and generates structured plans for parallel execution. CX Codex ★ 1,472repo stars oma-bootstrap oma-bootstrap is a Claude Code skill that checks whether oma, required providers, and project state are ready for a task. It runs before a skill or workflow that needs an oma command. CX Codex +1 ★ 1,472repo stars research-explorer research-explorer — a subagent that answers research questions by searching three planes at once: docs and code, market signals, and academic literature. Returns findings with sources and confidence labels. CX Codex ★ 1,472repo stars

Project sponsors

Companies that keep this analytics open