This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
function flatten(ary) { | |
var ret = []; | |
for(var i = 0; i < ary.length; i++) { | |
if(Array.isArray(ary[i])) { | |
ret = ret.concat(flatten(ary[i])); | |
} else { | |
ret.push(ary[i]); | |
} | |
} | |
return ret; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
/* | |
Usage | |
import {useExcerpt} from '../../hooks/useExcerpt' | |
1. | |
Import or store long text in a variable | |
const text = 'some really long text' | |
2. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Production-Quality Rule: No Mock Data or Temporary Solutions | |
This rule mandates that all generated code must be fully production-ready. No mock data, placeholder values, or temporary quick-fix solutions are allowed. If a complete and robust solution isn’t achievable, the system must instead produce an error so that the issue can be addressed properly. | |
No Mock Data: | |
- Do not generate or include any mock data or dummy values in any code or example. | |
- All data should reflect real-world, applicable scenarios. | |
No Temporary Solutions: | |
- Avoid any hacky, provisional, or quick-fix implementations solely to get a server or app running. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Docker Container Restart Rule | |
Description: | |
This rule directs the AI to provide guidance for restarting Docker containers instead of suggesting direct docker commands. When a container restart is needed, the AI must indicate which container (based on the Dockerfile context) should be restarted and leave the manual execution to the user. Additionally, the AI should verify context to avoid incorrect suggestions such as "npm run dev" when the service is actually running inside a Docker container. | |
Guidelines: | |
Restart Relevant Docker Containers: | |
Analyze the Dockerfile to determine which container(s) are relevant for the current service. |
OlderNewer