example-mobile-patterns
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: example-mobile-patterns
description: TEMPLATE - Mobile development patterns. Copy and customize for your mobile framework (React Nati…
category: other
runtime: no special runtime
---
# example-mobile-patterns output preview
## PART A: Task fit
- Use case: TEMPLATE - Mobile development patterns. Copy and customize for your mobile framework (React Native, Flutter, Swift, Kotlin, etc.) Use when this capability is needed..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Skill Usage / Step 1: Choose Your Framework / Option A: React Native” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “TEMPLATE - Mobile development patterns. Copy and customize for your mobile framework (React Native, Flutter, Swift, Kotlin, etc.) Use when this capability is needed.”.
- **02** When the source has headings, the agent prioritizes “Skill Usage / Step 1: Choose Your Framework / Option A: React Native” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Skill Usage / Step 1: Choose Your Framework / Option A: React Native”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: example-mobile-patterns
description: TEMPLATE - Mobile development patterns. Copy and customize for your mobile framework (React Nati…
category: other
source: tomevault-io/skills-registry
---
# example-mobile-patterns
## When to use
- TEMPLATE - Mobile development patterns. Copy and customize for your mobile framework (React Native, Flutter, Swift, Ko…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Skill Usage / Step 1: Choose Your Framework / Option A: React Native” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "example-mobile-patterns" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Skill Usage / Step 1: Choose Your Framework / Option A: React Native
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} Mobile Patterns (TEMPLATE)
This is a TEMPLATE skill. Copy this directory and customize it for your mobile framework.
Quick reference for mobile development patterns. For detailed examples, see linked guides.
Skill Usage
| Aspect | Details |
|---|---|
| Consumer | subagent-mobile-architect |
| Purpose | Code patterns and examples for mobile implementation |
| Invocation | Subagents read this skill; NOT directly invocable by users |
| How to Customize | Replace examples below with your framework's patterns |
Step 1: Choose Your Framework
Replace this section with your framework-specific requirements:
Option A: React Native
// Example: Redux with hooks
import { useSelector, useDispatch } from 'react-redux'
const MyComponent = () => {
const data = useSelector(state => state.feature.data)
const dispatch = useDispatch()
return <View>...</View>
}
Option B: Flutter
// Example: Provider pattern
class MyWidget extends StatelessWidget {
@override
Widget build(BuildContext context) {
final data = Provider.of<DataModel>(context);
return Container(...);
}
}
Option C: Native iOS (Swift)
// Example: SwiftUI with @State
struct ContentView: View {
@State private var data: String = ""
var body: some View {
Text(data)
}
}
Option D: Native Android (Kotlin)
// Example: Jetpack Compose
@Composable
fun MyScreen(viewModel: MyViewModel = viewModel()) {
val data by viewModel.data.collectAsState()
Text(text = data)
}
Critical Stack Requirements (CUSTOMIZE THIS)
| Feature | Your Pattern | Not Allowed |
|---|---|---|
| State | [Your state management] | [What to avoid] |
| Navigation | [Your navigation library] | [What to avoid] |
| UI | [Your UI library] | [What to avoid] |
| Testing | [Your testing framework] | [What to avoid] |
Quick Patterns Reference (CUSTOMIZE THIS)
Component Structure
[Your framework's component structure example]
State Management
[Your state management pattern example]
Navigation
[Your navigation pattern example]
Testing
[Your testing pattern example]
Detailed Guides
When you need specific implementation details, read:
- component-patterns.md - Component templates and structure
- state-management.md - State management patterns
- navigation-patterns.md - Navigation flows
- testing-patterns.md - Testing strategies
Common Anti-Patterns to Avoid (CUSTOMIZE THIS)
Add framework-specific anti-patterns here:
- ❌ [Anti-pattern 1 for your framework]
- ❌ [Anti-pattern 2 for your framework]
- ❌ [Anti-pattern 3 for your framework]
Dependencies Reference (CUSTOMIZE THIS)
{
"your-framework": "Core framework",
"your-state-library": "State management",
"your-navigation-library": "Navigation",
"your-testing-framework": "Testing"
}
When to Consult This Skill
- Designing mobile component architecture
- Implementing state management
- Creating navigation flows
- Setting up mobile testing
- Platform-specific implementations
Customization Instructions
- Copy this directory to a new skill (e.g.,
mobile-react-native-patterns) - Update frontmatter with your skill name and description
- Replace all examples with your framework's patterns
- Create detailed guides in separate .md files
- Update the architect subagent to reference this skill
- Delete this template or move it to
drafts/skills/
Source: CarlosDanielDev/maestro — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review