Menü
Mandatory rule to never use deprecated APIs or ignore deprecation warnings.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Mandatory rules and components for handling keyboard avoidance smoothly in the React Native app.
How to correctly handle and format protobuf Timestamp dates sent by the API Gateway to prevent "Invalid Date" issues.
Senior-level React Native architecture and patterns for Expo 54 apps.
Strict coding standards, naming conventions, file size limits, and typing rules.
Guidelines for managing server state, queries, and API clients in React Native.
Best practices for implementing forms with React Hook Form and Zod.
| name | React Native No Deprecated |
| description | Mandatory rule to never use deprecated APIs or ignore deprecation warnings. |
This project enforces a strict zero-deprecation policy to ensure the codebase remains maintainable, secure, and compatible with future library updates.
You must never introduce new usages of deprecated APIs, functions, enums, or libraries. Always consult the library's documentation to find the recommended modern alternative.
Do NOT use // eslint-disable-next-line @typescript-eslint/no-deprecated or any similar comments to bypass deprecation warnings. Bypassing these warnings is strictly prohibited.
If you encounter existing code that relies on deprecated features or uses an eslint disable comment for deprecations, you must refactor it to use the modern equivalent.
nativeEnum❌ Incorrect (Deprecated)
const schema = z.object({
type: z.nativeEnum(EventType),
});
✅ Correct (Modern API)
const schema = z.object({
type: z.enum(Object.values(EventType) as [string, ...string[]]),
});
[!CAUTION] Using deprecated features accumulates technical debt and increases the risk of breaking changes in future dependency upgrades. Always fix the root cause instead of suppressing the warning.