lists
Skill4 starsChanged 6 months agoMITView on GitHub
Use when implementing list-based UI. Covers ForEach identity, swipe actions, pull-to-refresh, custom styling, enumerated sequences.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- eddmann/jeevestheir own version, first seen Oct 8, 2026
- aspose-words/agentic-net-examplestheir own version, first seen Sep 9, 2026
- ztnkv/personal-operating-systemtheir own version, first seen May 12, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- aspose-words/agentic-net-examples★ 4same name
- eddmann/jeeves★ 2same name
- ztnkv/personal-operating-system★ 0same name
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.
In this repository76 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/components.mdcCursor rule
- .cursor/rules/currency.mdcCursor rule
- .cursor/rules/design-system.mdcCursor rule
- .cursor/rules/file-structure.mdcCursor rule
- .cursor/rules/forbidden-patterns.mdcCursor rule
- .cursor/rules/mvvm-architecture.mdcCursor rule
- .cursor/rules/pricing-display.mdcCursor rule
- .cursor/rules/scope.mdcCursor rule
- .cursor/rules/swift-conventions.mdcCursor rule
- accessibilitySkill
- animationsSkill
- apple-developer-authSkill
- apple-signinSkill
- app-store-preflightSkill
- asc-app-create-uiSkill
- asc-aso-auditSkill
- asc-build-lifecycleSkill
- asc-cli-usageSkill
- asc-crash-triageSkill
- asc-id-resolverSkill
- asc-localize-metadataSkill
- asc-metadata-syncSkill
- asc-metadata-yamlSkill
- asc-notarizationSkill
- asc-ppp-pricingSkill
- asc-release-flowSkill
- asc-revenuecat-catalog-syncSkill
- asc-screenshot-resizeSkill
- asc-shots-pipelineSkill
- asc-signing-setupSkill
- ascSkill
- asc-submission-healthSkill
- asc-subscription-localizationSkill
- asc-testflight-orchestrationSkill
- asc-wall-submitSkill
- asc-whats-new-writerSkill
- asc-workflowSkill
- asc-xcode-buildSkill
- billing-finance-calculatorSkill
- buildSkill
- business-modelSkill
- chartsSkill
- consolidate-errorsSkill
- content-composerSkill
- crashSkill
- debuggingSkill
- feature-directory-structureSkill
- feedback-statesSkill
- fix-errorSkill
- formsSkill
- foundation-modelsSkill
- hapticsSkill
- healthkitSkill
- layoutSkill
- navigationSkill
- notificationsSkill
- onboarding-questionnaireSkill
- onboardingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this guide when implementing or modifying list-based UI.
- Very specific: line 11
Always provide stable identity.
- Distinctive: line 75
Always convert to array:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
Files
List Patterns
Use this guide when implementing or modifying list-based UI.
ForEach Identity (CRITICAL)
Always provide stable identity. Never use .indices for dynamic content:
// CORRECT — stable identity via Identifiable
ForEach(users) { user in
UserRow(user: user)
}
// CORRECT — stable identity via keypath
ForEach(users, id: \.userId) { user in
UserRow(user: user)
}
// WRONG — indices create static content, crashes on removal
ForEach(users.indices, id: \.self) { index in
UserRow(user: users[index])
}Constant View Count per Element
// CORRECT — consistent view count
ForEach(items) { item in
ItemRow(item: item)
}
// WRONG — variable view count breaks identity
ForEach(items) { item in
if item.isSpecial {
SpecialRow(item: item)
DetailRow(item: item)
} else {
RegularRow(item: item)
}
}Avoid Inline Filtering
// WRONG — unstable identity
ForEach(items.filter { $0.isEnabled }) { item in ... }
// CORRECT — prefilter via computed property
var enabledItems: [Item] {
items.filter { $0.isEnabled }
}
ForEach(enabledItems) { item in ... }No AnyView in Rows
// WRONG — hides identity
AnyView(item.isSpecial ? SpecialRow(item: item) : RegularRow(item: item))
// CORRECT — unified row view with internal branching
struct ItemRow: View {
let item: Item
var body: some View {
if item.isSpecial { SpecialRow(item: item) }
else { RegularRow(item: item) }
}
}Enumerated Sequences
Always convert to array:
ForEach(Array(items.enumerated()), id: \.offset) { index, item in
Text("\(index): \(item)")
}Pull-to-Refresh
List(items) { item in
ItemRow(item: item)
}
.refreshable { await loadItems() }Custom List Styling
List(items) { item in
ItemRow(item: item)
.listRowInsets(EdgeInsets(top: 8, leading: 16, bottom: 8, trailing: 16))
.listRowSeparator(.hidden)
}
.listStyle(.plain)
.scrollContentBackground(.hidden)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
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.

