agentleFS
Sign inStart free
wanggang316wanggang316/you-skill-ios/AGENTS.md

you-skill-ios

AGENTS.md2 starsChanged 13 days agoMITView on GitHub

This project follows a layered domain architecture. See Architecture for the full domain model, layer structure, and dependency rules. See Golden Rules for the complete list with rationale and enforcement. All project knowledge lives in docs/. Start with the area relevant to your task: For simulator acceptance, Duo display checks, store screenshots, and submission, see iOS release workflow.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. wanggang316/youskill-ios★ 2100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All project knowledge lives in docs/.

    line 53
  2. Very specific:

    Before making changes, read the relevant design doc in docs/design-docs/

    line 67
  3. Very specific:

    Run harness check before submitting PRs

    line 69
  4. Distinctive:

    Follow the layer dependency rules in docs/architecture.md

    line 70
  5. Distinctive:

    When something fails, ask: "What capability is missing?" — then add it

    line 71
  6. Very specific:

    Run harness check to validate project structure and documentation.

    line 89
  7. Distinctive:

    When writing complex features or significant refactors, use an ExecPlan (exec-plan skill) from design to implementation.

    line 93

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

youskill-ios

Quick Start

xcodegen generate
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer swift test
# requires iOS platform/runtime installed in Xcode
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild -project YouSkill.xcodeproj -scheme YouSkill -destination 'generic/platform=iOS Simulator' build

Architecture Overview

<!-- Describe high-level system architecture in 3-5 sentences --><!-- See docs/architecture.md for detailed layer definitions and dependency rules -->

This project follows a layered domain architecture. See Architecture for the full domain model, layer structure, and dependency rules.

Repository Structure

youskill-ios/
├── Sources/               # Swift source organized by architecture layers
├── Tests/                 # Shared logic and repository tests
├── Assets.xcassets/       # App colors and icons
├── project.yml            # XcodeGen project manifest
├── YouSkill.xcodeproj/    # Generated Xcode project
├── docs/                  # System of record for all project knowledge
│   ├── architecture.md    # Domain model, layers, dependency rules
│   ├── golden-rules.md    # Numbered principles (enforced by harness check)
│   ├── design-docs/       # Design documentation for features and systems
│   ├── exec-plans/        # Versioned execution plans with progress tracking
│   ├── product-specs/     # Product specifications and requirements
│   ├── references/        # External references and integration notes
│   └── generated/         # Auto-generated artifacts (do not edit)
├── .opencode/agents/      # OpenCode subagents (reviewer, planner, sweep)
├── .claude/agents/        # Claude Code subagents (mirrors .opencode/agents/)
└── .harness/rules/        # Custom lint rules (YAML)

Golden Rules

  1. AGENTS.md is a map, not a manual — keep this file under 150 lines
  2. Validate boundaries — parse and validate data at system edges, never probe
  3. Prefer shared utilities — centralize invariants, avoid hand-rolled duplicates
  4. Every decision gets logged — use ExecPlans (exec-plan skill) for complex work
  5. Fix the environment, not the prompt — when agents struggle, add missing tools/docs/guardrails

See Golden Rules for the complete list with rationale and enforcement.

Documentation

All project knowledge lives in docs/. Start with the area relevant to your task:

DirectoryPurpose
docs/architecture.mdSystem architecture, domains, layers
docs/golden-rules.mdEnforced principles and conventions
docs/design-docs/Design documentation for features
docs/exec-plans/Execution plans for complex work
docs/product-specs/Product specifications
docs/references/External docs, API references
docs/generated/Auto-generated artifacts

Working with This Repository

  • Before making changes, read the relevant design doc in docs/design-docs/
  • For complex work, create an ExecPlan using the exec-plan skill
  • Run harness check before submitting PRs
  • Follow the layer dependency rules in docs/architecture.md
  • When something fails, ask: "What capability is missing?" — then add it

Build & Test Commands

For simulator acceptance, Duo display checks, store screenshots, and submission, see iOS release workflow.

xcodegen generate
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer swift test
# requires iOS platform/runtime installed in Xcode
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild -project YouSkill.xcodeproj -scheme YouSkill -destination 'generic/platform=iOS Simulator' build

Code Style & Conventions

<!-- Link to your linter config, formatting rules, naming conventions --><!-- These should be mechanically enforced, not just documented -->

Run harness check to validate project structure and documentation.

ExecPlans

When writing complex features or significant refactors, use an ExecPlan (exec-plan skill) from design to implementation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free