All skills
simota avatar

/compete

@35ffd55
by shingo imotasimota/agent-skills85 stars
15

Triggers when researching competitive or professional positioning: market intelligence, engineer brands, profiles, and content strategy. Research and strategy only — not code.

Use this Skill: https://skilld.dev/gh/simota/agent-skills/compete

This session only. Nothing lands on disk.

referenceai-era-strategy.md

≈3.6k tokens on demand. Your agent reads this file only when SKILL.md points to it.

AI-Era Engineer Branding Strategy

Purpose: Positioning, differentiation, and content strategy for engineers in the AI-augmented era (2025-2026+). Read when: Any mode — AI-era context should inform all branding decisions.


The Fundamental Shift

From "Engineer" to "Builder"

The role definition is evolving. Key industry voices:

Expert Affiliation Core Message
Boris Cherny Anthropic "Coding is effectively solved. The title 'software engineer' itself will disappear."
Hadi Partovi Code.org "Future engineer = software architect + technical PM fusion."
Amjad Masad Replit CEO "Roles evolve toward generalist product people, problem solvers, or systems people."
Kent Beck — "AI devalues language expertise but amplifies vision, strategy, and feedback loops."
Addy Osmani Google "AI handles 70% but the remaining 30% — edge cases, production quality — is where human expertise is decisive."
Gergely Orosz Pragmatic Engineer "Product orientation becomes a baseline requirement at startups."

Sources: pragmaticengineer.com, time.com, sfstandard.com, addyosmani.com

Value Depreciation vs Appreciation

Depreciating Appreciating
Multi-language fluency (AI generates in any language) Product thinking ("why build this?")
Frontend/backend specialization System design & architecture
Prototyping speed (non-engineers can now prototype) Code review & verification of AI output
Spec-to-implementation translation Technical leadership & mentoring
Boilerplate & CRUD implementation Domain expertise × technology intersection
Memorized syntax & patterns Judgment: when to trust AI, when to question

The 70/30 Rule (Addy Osmani)

AI completes ~70% of coding tasks. The remaining 30% — edge cases, production-grade quality, security, scalability — requires human expertise and is the most difficult part.

Branding implication: Position yourself in the 30% zone. Don't brand as "fast coder" — brand as the engineer who ensures the 70% actually works in production.


AI-Era Positioning Framework

Extended Tech × Domain × Perspective Model

Add a 4th dimension for AI-era differentiation:

Tech:        [Your primary technology/stack]
Domain:      [Your industry/problem space]
Perspective: [Your unique viewpoint]
AI-Stance:   [Your relationship with AI tools]

AI-Stance Dimension

Stance Description Positioning Example
AI Orchestrator Designs systems where AI is a component "LLMを組み込んだプロダクションシステムの設計"
AI Quality Gate Ensures AI output meets production standards "AI生成コードの品質保証・セキュリティ検証"
AI Force Multiplier Uses AI to amplify team productivity "AIツール導入でチーム生産性を3倍にした実績"
AI-Domain Bridge Applies AI to specific domain problems "金融規制対応にLLMを適用する専門家"
AI Educator Teaches others to leverage AI effectively "エンジニア向けAI活用のベストプラクティス発信"

The New 10x Engineer

The definition of "10x engineer" has shifted from "codes 10x faster" to "force multiplier":

Old 10x = Individual coding speed

New 10x:
  2x — AI-assisted fast coding
  2x — Identifying high-leverage work
  2x — Unblocking others and amplifying team output

Source: techfounderstack.com

Branding implication: Brand around team/organizational impact, not personal coding speed.

3-Layer Impact Framework

Layer Focus Outcome
1x → 3x AI fluency + fundamentals Personal productivity
3x → 10x Judgment + systems thinking Project leadership
10x → 100x Amplifying others Organizational impact

The Productivity Perception Gap (Critical Warning)

A randomized controlled trial with 16 experienced OSS developers found:

  • AI users were actually 19% slower
  • But believed they were 20% faster
  • ~40 percentage point gap between perception and reality

Source: metr.org

Branding implication: Never claim "AI makes me X times faster" without hard data. Focus on outcome quality, not speed claims. This is now an anti-pattern (see AP-8 below).


AI-Era Content Strategy

What to Create

Content Type Why It Works Platform
AI tool comparison with real project data First-hand experience > generic reviews Qiita, Zenn, YouTube
"AI couldn't solve this" case studies Demonstrates the 30% human value Zenn, Blog
Architecture decisions with AI Shows judgment, not just code Zenn, note
AI-augmented development process documentation Transparency builds trust Blog, YouTube
Failure stories with AI tools Authenticity + lessons learned note, X threads
Before/After with AI Concrete impact demonstration YouTube, Reels
Team AI adoption playbooks Organizational impact proof note, LinkedIn

The Authenticity Imperative

AI-generated content is increasingly detected and rejected:

  • Only 26% of consumers prefer AI creator content (down from 60% in 2023)
  • 20%+ of YouTube recommendations are "AI slop"
  • Audiences crave "human messiness" — imperfection signals authenticity

Sources: digiday.com, techradar.com

5 Elements AI Cannot Replicate

  1. Messiness and imperfection — Perfect prose reads as AI-generated
  2. Personal failure stories — Machines can't authentically share lessons from mistakes
  3. Unique perspective with emotional context — AI text "reads cold"
  4. Intentionality expression — Demonstrating thoughtful, deliberate choices
  5. Visible thinking process — Not just conclusions, but "how I arrived at this judgment"

AI Content Spectrum: Where to Position

Full AI-Generated ←————————————————→ Full Human-Created
      ❌ Low trust                        ✅ High trust

Recommended zone: "AI-Assisted SME Content"
= Human expertise + AI execution support
= You provide: vision, judgment, experience, opinion
= AI provides: draft structure, research synthesis, formatting

Source: clearscope.io

Vibe Coding vs Spec-Driven Development

Approach Definition Risk Level
Vibe Coding Natural language → AI generates → accept without deep review High
Spec-Driven Development Specs as prompts → AI generates → human verifies Recommended

Branding implication: Position as someone who does spec-driven development, not vibe coding. Show that you understand and verify AI output.

Source: thoughtworks.com


Trust Signals for 2025-2026

New Credibility Indicators

Signal Why It Matters How to Build
Evidence of real work Podcast appearances, talk recordings, case studies Accept speaking invitations, publish retrospectives
Community endorsement What peers say about you matters more than self-claims Engage authentically, help others publicly
Consistent theme focus 3-5 topics repeated cross-platform Define content pillars, resist topic drift
Face and voice visibility Video builds trust that text cannot YouTube, conference talks, live streams
Owned channels Reduce algorithm dependency Newsletter, Discord, personal site
Numbers with context Specific outcomes, not vague claims "Reduced deploy time from 2h to 15min" not "improved efficiency"

From Vanity Metrics to Trust Metrics

Old (Vanity) New (Trust)
Follower count Engagement depth (replies, DMs, referrals)
Post impressions Content saves and shares
Stars on GitHub Dependents, contributors, real usage
"AI-powered" label Concrete AI-assisted outcomes with data
Speed claims Quality and reliability evidence

Content Authentication Trend (C2PA)

Digital provenance — cryptographic proof of content origin — is becoming industry standard:

  • C2PA (Coalition for Content Provenance and Authenticity) has 6,000+ members
  • Hardware integration: Google Pixel, Sony cameras
  • Future implication: "Human-verified" content may carry a trust premium

Sources: contentauthenticity.org, techradar.com


AI-Era Anti-Patterns (AP-8 ~ AP-11)

Supplement to core AP-1~AP-7:

AP-8: Productivity Theater

Signal: Claiming AI-driven speed improvements without data.

Detection Examples
Unverified speed claims "AI made me 10x faster" (e.g. "AIで10倍速くなった") without measurement
Tool name-dropping Listing every AI tool without showing results
Ignoring the perception gap Not acknowledging the 70/30 reality

Fix: Show concrete before/after metrics. Acknowledge AI limitations honestly.

AP-9: Vibe Coder Branding

Signal: Positioning as someone who "lets AI do everything."

Detection Examples
"I just prompt and ship" Implies no engineering judgment
No quality verification mentioned Suggests accepting AI output uncritically
Deprecating traditional skills "You don't need to understand code anymore"

Fix: Position as AI-augmented, not AI-dependent. Emphasize judgment, review, and quality.

AP-10: AI Expertise Inflation

Signal: Claiming AI/ML expertise based solely on using AI tools.

Detection Examples
"AI Engineer" title without ML background Using Copilot ≠ AI engineering expertise
Confusing tool usage with system design Building with LLM APIs ≠ designing LLM systems
Trend-chasing AI certifications Collecting badges without deep understanding

Fix: Be precise about your AI relationship (user vs builder vs researcher). Honesty builds more trust than inflated titles.

AP-11: Human Erasure

Signal: Content so polished by AI that personality disappears.

Detection Examples
Generic opening lines "In today's rapidly evolving landscape..."
Perfect grammar, zero personality Reads like documentation, not a human
No first-person experience All third-person, theoretical
Identical structure across posts Template-obvious formatting

Fix: Intentionally include rough edges, personal anecdotes, opinions, humor. Let 20% of your content be deliberately unpolished.


Japan-Specific AI-Era Considerations

Platform Strategy Adjustments

Platform AI-Era Shift
Qiita High demand for AI how-tos and tool comparisons. However, articles covering only "things you could just ask AI" are losing value
Zenn AI-era architecture discussions and design decision rationale are key differentiators. Book format for systematic coverage is strong
note "Career strategy in the AI era" and "behind-the-scenes of tech decisions" resonate with non-tech readers
X Breaking AI news and opinion sharing. Participating in discussions builds brand
YouTube Pair-programming with AI videos and live coding are the most effective for building trust

Japanese Tech Community Perspectives

  • Shift toward valuing "problem definition ability" — In an era where AI writes code, engineers who can define "what to build" are rising in value
  • Domain knowledge x technical skill multiplication — Deep understanding of specific industries (healthcare, finance, manufacturing, etc.) is hard for AI to replace
  • Value as "primary information sources" — In an era where AI aggregates information, creators with original experience and insights become rare
  • Pi-shaped skills — Evolution of T-shaped skills. Establish a unique position by combining multiple deep specializations

Content Ideas for Japanese Platforms

Theme Format Platform
"Skills that gain value in the AI era" Opinion article note, Zenn
"Claude Code/Cursor hands-on report" Implementation log Qiita, Zenn
"How to review AI-generated code" How-to Qiita, YouTube
"Vibe coding vs spec-driven development" Comparative analysis Zenn
"How team productivity changed after AI adoption" Results report note, LinkedIn
"Design decisions you should not delegate to AI" Experience-based essay Zenn, note
"Engineer career strategy in the AI era" Career essay note

Key Statistics (2025-2026)

Statistic Source
85% of developers use AI tools regularly (end of 2025) Pragmatic Engineer
70% use 2-4 AI tools simultaneously Pragmatic Engineer
Claude Code: #1 in usage and satisfaction (46%) Pragmatic Engineer
80% of programming jobs remain human-centered McKinsey
26% of consumers prefer AI creator content (down from 60% in 2023) Billion Dollar Boy
45% of engineering roles expect multi-domain proficiency by 2026 Brainhub
Employee posts get 8× more engagement than corporate channels Edelman
90% of online content predicted to be AI-synthesized by 2026 Industry estimates
Bluesky reached 41.4M users by end of 2025 (+302% YoY); Threads hit 400M MAU by Aug 2025 Sprout Social — Bluesky Statistics
LinkedIn newsletters generate 206% more impressions than standard posts, 4.40% engagement rate Buffer — LinkedIn Algorithm 2026

Actionable Checklist for AI-Era Branding

  1. ☐ Define your AI-Stance (Orchestrator / Quality Gate / Force Multiplier / Domain Bridge / Educator)
  2. ☐ Position in the "30% zone" — emphasize what AI can't do
  3. ☐ Create at least one "AI couldn't solve this" case study
  4. ☐ Document your AI-augmented development process transparently
  5. ☐ Include personal failure stories and rough edges in content
  6. ☐ Show team/organizational impact, not just personal productivity
  7. ☐ Use concrete metrics with context, not speed claims
  8. ☐ Maintain face/voice visibility (video, talks)
  9. ☐ Build owned channels (newsletter, personal site)
  10. ☐ Check AP-8~AP-11 on all outputs

Source: SKILL.md on GitHub

1 warning13d5 checks · Risk SAFE
  • Gen Agent Trust Hub13d

    The skill is a comprehensive market intelligence and professional branding tool designed for strategic analysis. It follows security best practices by explicitly requiring prompt-injection checks on data fetched from the web and emphasizes citations and evidence-backed research. No malicious patterns or security vulnerabilities were detected.

  • Socket13d

    No alerts

  • Snyk13d

    Risk: MEDIUM · 1 issue

  • Runlayer6mo

    9 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 35ffd55. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 2 weeks ago

README badge

README badge for simota/agent-skills/compete